Am 22.06.2016 um 15:08 schrieb Pierre Labastie:
You may try (outside chroot):
echo 'int main(){}' > dummy.c
/tools/bin/i686-lfs-linux-gnu-gcc dummy.c
readelf -l a.out | grep ': /tools'
[Requesting program interpreter: /tools/lib/ld-linux.so.2]
Also, another check: ls -i /tools/bin/i686-pc-linux-gnu-gcc /tools/bin/gcc
302801465 /tools/bin/gcc 302801465 /tools/bin/i686-pc-linux-gnu-gcc
Unfortunately I do not have anymore the log, as I erased the directory as advised. But I did unpack gcc-6.1.1 outside of chroot and made the configure for pass 2 ( without the first commands ). I do not know, if this helps but anyway, the result wasto check, that /tools/bin/gcc is linked to the right inode...Last but not least: do you have the "configure" log from gcc-pass2? If so, can you check the line beginning with "checking for gcc..."? It should be:checking for gcc... i686-lfs-linux-gnu-gcc
checking for gcc... gcc I hope this helps a little And thank you very much for the help, Edgar -- Dr.-Ing. Edgar Alwers <edgaralw...@gmx.de> GPG Key ID:AD5C6F70 -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
