Hi,
I've recently built LFS on a 32 bit system (Version SVN-20160622.)
When I got to 6.17 and issued the configure command I noticed that I was
getting
/tools/lib/gcc/i686-pc-linux-gnu/6.1.0/../../../../i686-pc-linux-gnu/bin/ld
as a result of "checking for ld..."
I was expecting the system to now be able to find and use the newly
installed ld from chapter 6.13. Thinking I had done something wrong I
retraced my steps but could see no issues with them.
So, I compared with this build log
http://www.linuxfromscratch.org/lfs/build-logs/development/core2duo/build-logs-2012-04-22/079-gcc
and this one also shows the same "oddity".
Eventually, I decided to run the gcc configure script prefixing it with
LD=ld.
I was unable to understand why the configure script would prefer the ld
in /tools and/or if this would be an important issue for the rest of the
book.
Regards,
Ed Batalha
--
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
