[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: flexlexer.h include path
From: |
Werner Scheinast |
Subject: |
Re: flexlexer.h include path |
Date: |
Wed, 1 Jun 2005 01:35:34 +0200 (CEST) |
Am 31.05.05 schrieb Han-WenNienhuys:
> which platform?
Sorry, I should have uploaded config.log instead of the mere output. Now
it is on http://www.scheinast.homepage.t-online.de/config.log
I have a SuSE 9.0 on i386 (pentium 4), with manual updates.
gcc (GCC) 3.3.1 (SuSE Linux)
AFPL Ghostscript 8.51 (2005-04-18)
bison (GNU Bison) 2.0
etc., well, most package details are in my configure output.
> this is very strange. Can you double check (using g++ -E) the g++ finds
> the FlexLexer.h in lily/out/ ?
I'm not sure what you mean. I manually called the last
g++ [many options] includable-lexer.cc
with the additional -E option. There was no output at all. But while
experimenting, I discovered that the build works after a "make clean".
To summarize:
tar -zxvf lilypond-2.5.26.tar.gz
cd lilypond-2.5.26
./configure
make
--> error message
make clean
make
--> works
"make clean" (or the "make" before) also removes some files included in
the original source package, especially these four in the directory
lily/out/: FlexLexer.h, lexer.cc, parser.cc, parser.hh
During the second "make" they are created again - or just copied
from my system includes (in case of FlexLexer.h).
So, my guess is that the first build attempt accesses one of these
original files, which leads to a conflict with the later dynamically
created ones.
The output of the second, successful make is now also on
http://www.scheinast.homepage.t-online.de/output2.make (0.9 MB) or
http://www.scheinast.homepage.t-online.de/output2.make.bz2 (70 kB)
hoping to have confused everyone
Werner