David Kastrup <d...@gnu.org> writes:

> David Kastrup <d...@gnu.org> writes:
>
>> James <pkx1...@gmail.com> writes:
>>
>>> Hello,
>>>
>>> --snip--
>>>
>>> rm -f ./out/lilypond-version.dep;
>>> DEPENDENCIES_OUTPUT="./out/lilypond-version.dep
>>> ./out/lilypond-version.o" g++ -c -Woverloaded-virtual
>>> -I/usr/include/python2.6 -I/usr/include/python2.6 -fno-strict-aliasing
>>>  -g -fwrapv     -DHAVE_CONFIG_H  -DNDEBUG
>>> -I/home/jlowe/lilypond-git/lily/include -I./out
>>> -I/home/jlowe/lilypond-git/flower/include -I../flower/./out
>>> -I../flower/include -I/home/jlowe/lilypond-git/lily/out  -O2
>>> -finline-functions -g -pipe -pthread -I/usr/include/freetype2
>>> -pthread -I/usr/include/pango-1.0 -I/usr/include/freetype2
>>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
>>> -Wno-pmf-conversions  -W -Wall -Wconversion -o out/lilypond-version.o
>>> /home/jlowe/lilypond-git/lily/lilypond-version.cc
>>> In file included from /home/jlowe/lilypond-git/lily/lily-lexer-scheme.cc:21:
>>> /home/jlowe/lilypond-git/lily/include/lily-lexer.hh:69: error: ISO C++
>>> forbids declaration of 'YYSTYPE' with no type
>>> /home/jlowe/lilypond-git/lily/include/lily-lexer.hh:69: error:
>>> expected ';' before '*' token
>>
>> That looks like something I would have committed.  I'll research.
>
> Does not make all that much sense: it complains about YYSTYPE not being
> defined.  But YYSTYPE is defined in lily/out/parser.hh (and has been
> defined there before) and lily-lexer.hh
> has
> #include "parser.hh"
>
> So unless this includes a different file "parser.hh" (but then why
> wouldn't other modules have the same problem?), I have no idea why this
> would happen.
>
> So no, I don't have an idea, and even after
>
>     make clean && ./autogen.sh && make
>
> stuff continues to work here.

With and without optimization.

Can you try what happens when you do a _single_ job build?  I think your
compiler considers absent include files unimportant, and if parser.hh
has not been created by the time lily-lexer.hh includes it, this would
cause problems like the above.

-- 
David Kastrup


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to