On 2004-09-01 at 12:49:11 [+0200], Axel Dörfler wrote: > Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote: > > On Wed, 1 Sep 2004, Axel Dörfler wrote: > > > Jérome DUVAL <korli@xxxxxxxx> wrote: > > >> the bash version in our repository is supposed to build correctly > > >> ... :) > > >> > > >> i don't know why there is a flex parse.h in your bash log build > > >> > > >> i have problems too : > > >> my libglob.a is built into the "make" objects dir > > >> > > >> can you reproduce your bug by doing "jam clean; jam" ? > > > > > > Yes, anytime. I did a "jam" in the bash directory as well as a "jam > > > bash" - both don't work. > > I suppose you mean `jam sh'? > > Yes, actually I did :-) > And this looks fishy: > > Yacc1 ../../../../objects/x86.R1/apps/bin/bash/parse.c ../../../../ > objects/x86.R1/apps/bin/flex/parse.h > conflicts: 1 shift/reduce > YaccMv ../../../../objects/x86.R1/apps/bin/bash/parse.c ../../../../ > objects/x86.R1/apps/bin/flex/parse.h > warning: using independent target <src!apps!bin!flex>parse.c > Yacc1 ../../../../objects/x86.R1/apps/bin/flex/parse.c ../../../../ > objects/x86.R1/apps/bin/flex/parse.h > YaccMv ../../../../objects/x86.R1/apps/bin/flex/parse.c ../../../../ > objects/x86.R1/apps/bin/flex/parse.h > > > > I am using our latest Jam, too. > > Weird, as I said everything works fine for me. Can you send me the > > output > > of a `jam -d3 sh', please. I think, we can take this off list. > > Okay, thanks! > You'll get it. It seems, you're using an old version of Jam. The bug in the Yacc rule in Jambase that causes your problem has been fixed by Jérome in revision 1.10: http://cvs.sourceforge.net/viewcvs.py/open-beos/current/src/tools/jam/Jambase?rev=1.11&view=log That bug exists also in the vanilla Perforce Jam version 2.5rc3 (and earlier). So at the moment it is recommended to use only the version from the HEAD of our repository (aka the main trunk). CU, Ingo