Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#20 Bison says broken pipe during make on Fedora Core

closed
None
5
2014-08-20
2004-04-21
Anonymous
No

$ make
make all-recursive
make[1]: Entering directory `/home/hc/src/aide-0.10'
Making all in src
make[2]: Entering directory `/home/hc/src/aide-0.10/src'
bison -y -d -p conf -o conf_yacc.c
/home/hc/src/aide-0.10/src/conf_yacc.y
make[2]: *** [conf_yacc.c] Broken pipe
make[2]: Leaving directory `/home/hc/src/aide-0.10/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/hc/src/aide-0.10'
make: *** [all-recursive-am] Error 2

Contact: hc (at) saustrup (dot) net

Discussion

  • Logged In: YES
    user_id=330646

    Which version of bison are you using? Please post the output
    of "bison --version" and make sure you have at least version
    1.875a.

     
    • assigned_to: nobody --> rvdb
    • summary: Bison says "broken pipe" during make on Fedora Core --> Bison says
    • status: open --> pending
     
  • Logged In: YES
    user_id=751962

    $ bison --version
    bison (GNU Bison) 1.875

    $ rpm -qi bison
    Name : bison Relocations:
    (not relocateable)
    Version : 1.875 Vendor:
    Red Hat, Inc.
    Release : 5 Build Date:
    Wed 24 Sep 2003 11:56:36 PM CEST

     
    • summary: Bison says --> Bison says broken pipe during make on Fedora Core
     
  • Logged In: YES
    user_id=330646

    Can you run the bison command by hand, to make sure it is
    bison that fails? If it is, try upgrading to bison-1.875-7.1
    and see if the problem persists.

     
  • Logged In: YES
    user_id=751962

    $ bison -y -d -p conf -o conf_yacc.c
    /home/hc/src/aide-0.10/src/conf_yacc.y
    Broken pipe

    Output from strace:
    write(4, "m4_init()\nm4_define([b4_actions]"..., 4096) = -1
    EPIPE (Broken pipe)
    --- SIGPIPE (Broken pipe) @ 0 (0) ---
    +++ killed by SIGPIPE +++

    Problem went away after installing the m4 package. Maybe
    configure should check for this?

     
  • Logged In: YES
    user_id=330646

    Under debian, bison depends on m4. I suppose it is the same
    on Fedora. It sounds like you had a misconfigured system.
    This would also explain why bison crashed instead of
    reporting the problem.

     
    • status: pending --> closed