Not sure whether I made a copy/paste error in my previous post, so I re-ran Chapter 5. The output from the sanity check at 5.10.1 is: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]
So that should be correct, right? I then moved on to Chapter 6 and I got the exact same results as I described in my previous post. Any idea what is wrong with the sanity check at 6.17? Everything looks fine at 6.10 and then zlib, file, binutils, gmp, mpfr, and mpc build and test fine. Then I build gcc and do the sanity check and get the weird results in 6.17. From: "Chris Staub" <[email protected]> To: "lfs-support" <[email protected]> Sent: Thursday, October 8, 2015 3:32:17 AM Subject: Re: [lfs-support] GCC Insanity Check On 10/07/2015 08:24 PM, Paul Sturm wrote: > I am building LFS 7.8 64-bit in a virtualbox VM. My sanity check is > failing in 6.17. Here are the details: > > /tools build fine in Chapter 5 and all tests pass. > > *Sanity checks for 5.7.1: * > [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] > > *and 5.10.1:* > [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2] Is this accurate? If so, this is not what it should be, and in fact I would be surprised if you managed to chroot at all if this were the case. -- 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
-- 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
