[lfs-dev] Wording fix
matthew at linuxfromscratch.org
Mon May 7 16:04:59 PDT 2012
On Sat, 2012-05-05 at 10:35 -0400, Jeremy Huntwork wrote:
> On May 5, 2012, at 10:24 AM, Jeremy Huntwork
> <jhuntwork at lightcubesolutions.com> wrote:
> > Looks like I missed some necessary text changes.
> There's also this statement made regarding the fixincludes script in
> GCC pass 2: "In fact, running this script may actually pollute the
> build environment by installing fixed headers from the host system
> into GCC's private include directory"
> That may no longer be true. In fact it would be nice if we can confirm
> this. Anyone willing to poke a bit there and see if touching this
> fixincludes script is still necessary?
Here's what the fixincludes script resulted in with my latest build:
│ ├── limits.h
│ ├── linux
│ │ └── a.out.h
│ ├── README
│ └── syslimits.h
There's a comment in linux/a.out.h that it fixed
up /tools/include/a.out.h so that looks OK. syslimits.h just includes
limits.sh, so that looks fine too. limits.h has been fixed but there's
no indication of which limits.h was used as input to it. I can only
assume it was /tools/include/limits.h due to the a.out.h fix and the
fact that no other headers from my host's devel packages have ended up
being fixed up.
Chapter 6 is in the process of building now, so I'll update again
tomorrow when I have the results.
More information about the lfs-dev