chapter 6.16: configure: error: in `/sources/gcc-build/i686-pc-linux-gnu/libgcc':, ... C preprocessor "/lib/cpp" fails sanity check

Bruce Dubbs bruce.dubbs at
Wed May 26 10:19:54 PDT 2010

Neal Murphy wrote:
> On Wednesday 26 May 2010 08:33:20 linux fan wrote:
>> On 5/26/10, Simon Geard <delgarde at> wrote:
>>> I can't really see how things can be improved (short of blinking red
>>> text on *every* page), but it does seem like half the problems we deal
>>> with are from people not following it. Are people not even reading that
>>> entire "General Compilation Instructions" page, and skipping straight to
>>> the packages?
>> The important note #1 in ch 5.3 is clear.
>> However, "General Compilation Instructions"  never specifies the flow
>> of events expected to follow:
>> 1 - make sure $LFS is set to the target directory (export LFS=/mnt/lfs)
>> 2 - change directory to $LFS/sources
>> 3 - unpack the package tarball
>> 4 - change directory to the unpacked directory created by tar
>> 5 - follow package build and install instructions
>> 6 - change directory to $LFS/sources
>> 7 - remove the unpacked directory created by tar

We don't have it in a list, but it is in Section 5.3.  I even put in a 
note as the very first thing in Binutils:


Go back and re-read the notes in the previous section. Understanding the 
notes labeled important will save you a lot of problems later.

I guess I'll need to reemphasize some more.  :(

   -- Bruce

More information about the lfs-support mailing list