This is the output:
attempt to open /home/lfs/cross-tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so failed
attempt to open /home/lfs/cross-tools/bin/../lib/gcc/libgcc_s.so failed
attempt to open /cross-tools/lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so succeeded
/libgcc_s.so)
I ran the test as well, and here is my output:
echo 'main(){}' > dummy.c
i686-pc-linux-gnu-gcc -Wl,--verbose dummy.c 2>&1 |grep libgcc_s.soattempt to open /home/lfs/cross-tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so failed
attempt to open /home/lfs/cross-tools/bin/../lib/gcc/libgcc_s.so failed
attempt to open /cross-tools/lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc_s.so failed
attempt to open /home/lfs/cross-tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/lib/libgcc_s.so succeeded
-lgcc_s (/home/lfs/cross-tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/lib/libgcc_s.so)
I can see that it looks in /usr/lib but doesn't find the libgcc_s.so. As you implied, likely because I haven't done any other cross-compiling on this machine save for what the cross-lfs book does.
I'm not sure that this is a major concern - however I too would prefer to see that it *always* find the libgcc_s.so in /cross-tools
I'll add your sed into the next revision, thanks.
-- Jeremy Huntwork -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
