bug-lilypond
[Top][All Lists]
Advanced

[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: Fri, 3 Jun 2005 01:12:03 +0200 (CEST)

Am 01.06.05 schrieb Werner Scheinast:

> "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.

I had another look at this.

First, thanks for removing the spurious configure warning about flex in 
2.5.27. But the actual bug persists with that new release:
The first time build fails because of an incompatibility with my flex 
version 2.5.31. lily/includable-lexer.cc employs some variables 
(yy_buffer_stack, yy_buffer_stack_top) that are not declared in the 
lily/out/FlexLexer.h delivered with lilypond, but they are declared in 
my /usr/include/FlexLexer.h. For some strange reason, the former is 
included in lily/includable-lexer.cc _before_ it is overwritten by the 
latter.
In fact, when I delete FlexLexer.h and lexer.cc in lily/out/ before the 
build, it works with the first attempt. Therefore my question:
Are these files needed for anything?
If not, please omit them from the source package. If yes, they should be 
overwritten _before_ compiling lily/includable-lexer.cc in the build 
process, if possible.

By the way, is anybody out there who also observed such thing with a new 
flex version, probably >=2.5.29?

nightly regards
Werner




reply via email to

[Prev in Thread] Current Thread [Next in Thread]