Dan Nicholson wrote:
On 3/7/06, Dominic Ringuet <[EMAIL PROTECTED]> wrote:
There is always the exception in exceptional environment, but:
SPECFILE=`dirname $(gcc -print-libgcc-file-name)`/specs &&
gcc -dumpspecs > $SPECFILE &&
unset SPECFILE
What is the value of SPECFILE? Is this the whole command? Where's the sed?
That is to intently put a sane specs file on the host.
then start building chapter 5; tcl, expect and dejagnu will be linked to
/tools/lib/ld-linux.so.2 wich is fine.
after the second pass of gcc 4.0.2:
readelf -l /tools/bin/gcc|grep ld-linux.so.2 -> /tools/lib/ld-linux.so.2
[OK]
after the second pass of binutils 2.16.1:
readelf -l /tools/bin/ld|grep ld-linux.so.2 -> /lib/ld-linux.so.2
[FAIL]
This is very weird. Things have definitely gone wrong here. Could
you do the basic sanity check with dummy.c instead of the installed
files? Try at each of the above stages.
chapter 5.7 adjusting the toolchain
dummy.c: readelf -l|grep ld-linux.so.2: /tools/lib/ld-linux.so.2
chapter 5.11 gcc-pass2
dummy.c: readelf -l|grep ld-linux.so.2: /tools/lib/ld-linux.so.2
chapter 5.12 binutils-pass2
dummy.c: readelf -l|grep ld-linux.so.2: /lib/ld-linux.so.2
By the way, which version of the book are you using? It looks like
the current SVN.
Yes, current SVN. Good guess.
I can't test with any other system and building takes time so I can't
tell right now if reinserting the file will reproduce the bug. But I can
tell for sure that removing /usr/lib/gcc/i686-pc-linux-gnu/specs did
fixed my '/tools/bin/env /tools/bin/bash: no such file or directory'
problem upon entering chroot in chapter 6.
Either you're writing to /usr/lib/gcc/.../specs, or the host system
has installed a specs file, which is unlikely. What is your host
system?
Even if unlikely, you're right; that is the whole point as I can see.
The host is november 2005 SVN. I had problems with the linker and that's
probably when the specs file got there.
I am usually a very silent mailing list reader and don't want to make
noise that is not useful.
This is useful. My initial reaction is that you've overlooked
something, but this discussion could help to make the build more
robust, regardless.
--
Dan
At the end, this is probably my host who should'nt had this specs file.
May be some distros use it. May be not and I'm an isolated case. Still
gcc, if not binutils, did some strange behavior. I'll check through both
./configure for references to /usr/lib/gcc/i686-pc-linux-gnu/specs. If
the problem is tracked back, I'll even try my hands on a patch.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
