mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-07-09 13:59:51 +01:00
added fixincludes explanation
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2180 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
d066924831
commit
ac68bd3dd2
@ -7,7 +7,17 @@ This patch fixes a few bugs. In particular it contains the "copy fix" and
|
|||||||
<ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para>
|
<ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para>
|
||||||
|
|
||||||
<para><userinput>patch -Np1 -i ../gcc-3.2-nofixincludes-2.patch:</userinput>
|
<para><userinput>patch -Np1 -i ../gcc-3.2-nofixincludes-2.patch:</userinput>
|
||||||
This prevents the fixincludes script from running.</para>
|
This prevents the fixincludes script from running. This is needed because
|
||||||
|
under normal circumstances the GCC installation will run the fixincludes
|
||||||
|
scripts which scans your system for header files that need to be fixed. Say
|
||||||
|
it finds Glibc header files. It will fix them and will end up in
|
||||||
|
$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2. Later on in chapter 6 you
|
||||||
|
will install Glibc which will install header files in /usr/include. Next
|
||||||
|
you will install other programs which will use Glibc headers. GCC will look
|
||||||
|
in /static/lib/gcc-lib before looking in /usr/include, whichhas the result
|
||||||
|
of Glibc header files from your host distribution being found and used which
|
||||||
|
are probably incompatible with the Glibc version actually in use on the LFS
|
||||||
|
system.</para>
|
||||||
|
|
||||||
<para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard
|
<para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard
|
||||||
codes some paths while compiling and so we need to pass /static as the
|
codes some paths while compiling and so we need to pass /static as the
|
||||||
|
Loading…
Reference in New Issue
Block a user