Just got back from vacation. On 3/29/07, yayo <[EMAIL PROTECTED]> wrote: > hey Dan! > guess what...? > it works now! :D
That's great! Thanks very much for looking into this. > look at this session. I've compiled and installed bison 2.2 and bash > yesterday, > before to go sleep, and I made this test today: <snip> > [EMAIL PROTECTED]:/mnt/lfs/sources$ bison --version > bison (GNU Bison) 2.2 > Written by Robert Corbett and Richard Stallman. > > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > [EMAIL PROTECTED]:/mnt/lfs/sources$ cat > test.sh << "EOF" > >#!/tools/bin/sh > >set ./lib ./lib/auto > >for dir do > >echo $dir > >done > >EOF > [EMAIL PROTECTED]:/mnt/lfs/sources$ /tools/bin/sh -x ./test.sh > + set ./lib ./lib/auto > + for dir in '"$@"' > + echo ./lib > ./lib > + for dir in '"$@"' > + echo ./lib/auto > ./lib/auto > [EMAIL PROTECTED]:/mnt/lfs/sources$ Yep, this is what you should see. I think you already said the same, but with bison-1.75, you get the bad output that looks something like: for dir in '' right? > well, to be honest I still didn't compiled/installed perl. > I preferred to wait to fix this before, to be sure the system was ok. :P > But I'll do it tonight. And I'm sure this time it will be ok! > Thanks a lot! Confirming that perl actually builds would be nice, but I'm fairly confident that this is the source of the issue. > I dunno if I'll have the time to download all the previous versions of bison > to test them all, along with bash. That's OK. Now that we've isolated the problem, I can probably run through this test pretty quickly. I mostly just wanted to know that this was really the problem before spending a bunch more time testing this. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
