Summary: | LS build fails in src/network/lscp.y with bison 2.4 | ||
---|---|---|---|
Product: | LinuxSampler | Reporter: | Juuso Alasuutari <juuso.alasuutari> |
Component: | other | Assignee: | Andreas Persson <andreas56> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | SVN Trunk | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: |
lscpparser.cpp
lscpsymbols.h |
Description
Juuso Alasuutari
2008-12-07 16:30:34 CET
Probably the auto-generated LSCP parser was not automatically re-generated of the new LSCP definition file (lscp.y). Try: make parser make from the toplevel directory. I think it's already generated during 'make -f Makefile.cvs' because I see this: Searching for a parser generator...OK (/usr/bin/bison -y) Generating LSCP parser... I tried manually running 'make parser' after ./configure but that didn't affect the outcome from make. Are you sure bison did not throw out any error message? What is the full output of "make parser"? Please also try to make a completely fresh checkout of LS from CVS and try to build it again. If that doesn't work, please upload your two auto generated files lscpparser.cpp and lscpsymbols.h. Created attachment 41 [details]
lscpparser.cpp
Created attachment 42 [details]
lscpsymbols.h
The checkout is completely fresh. Here's the output from 'make parser' and the two files you requested (attached). make[1]: Entering directory `~/tmp/linuxsampler-cvs/src/network' ../../scripts/generate_parser.sh Searching for a parser generator...OK (/usr/bin/bison -y) Generating LSCP parser... conflicts: 1801 shift/reduce, 1045 reduce/reduce conflicts: 1801 shift/reduce, 1045 reduce/reduce Done Updating Documentation/lscp.xml...Done make[1]: Leaving directory `~/tmp/linuxsampler-cvs/src/network' Well, what do you know. Downgrading bison from 2.4 to 2.3 makes the problem go away. I apologize for the trouble, I was sloppy for initially blaming flex and then slow looking into bison versions. Of course bison 2.4 still thinks that lscp.y is broken. Does the error with bison 2.4 go away if you add #include "lscpsymbols.h" to lscp.y? Yes, adding that include seems to fix it. Marking this one as blocker, as it should be resolved before the upcoming release. Fix committed to CVS. |