From 7681a57ae95583421fc47a79859aedfe17a76050 Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Sat, 11 Jan 2003 18:04:52 +0000 Subject: Redid GCC installation page git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2314 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/gcc-exp.xml | 38 --------------------- chapter05/gcc-inst.xml | 93 +++++++++++++++++++++++++++++++++++++++++++++----- chapter05/gcc.xml | 5 ++- 3 files changed, 87 insertions(+), 49 deletions(-) delete mode 100644 chapter05/gcc-exp.xml (limited to 'chapter05') diff --git a/chapter05/gcc-exp.xml b/chapter05/gcc-exp.xml deleted file mode 100644 index 051d13d14..000000000 --- a/chapter05/gcc-exp.xml +++ /dev/null @@ -1,38 +0,0 @@ - -Command explanations - ---prefix=/static: This is NOT a typo. GCC hard -codes some paths while compiling and so we need to pass /static as the -prefix during ./configure. We pass the real install prefix during the -make install command later. - ---with-as and --with-ld: GCC can be -miscompiled if your host distribution's Binutils package is quite old. We -need a good working static GCC until we reinstall GCC later in chapter 6. -So by using as and ld from the -Binutils package we just compiled we ensure that GCC will work -correctly. - -make BOOT_LDFLAGS="-static": -This is the equivalent to make LDFLAGS="-static" as we use with other -packages to compile them statically. - -make install-no-fixedincludes: -This prevents the fixincludes script from running. Preventing this is -necessary because under normal circumstances the GCC installation will run -the fixincludes script which scans your system for header files that need to -be fixed. It might find that the Glibc header files of your host system need -to be fixed. If so, it will fix them and put them in -$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2. -Later on in chapter 6 you will install Glibc which will put its header -files in /usr/include. Next you will install other -programs that use the Glibc headers. GCC will look in -/static/lib/gcc-lib before looking in -/usr/include, with the result of finding and using -the fixed Glibc header files from your host distribution, which are probably -incompatible with the Glibc version actually used on the LFS system. - -ln -s gcc $LFS/static/bin/cc: This -creates the $LFS/static/bin/gcc symlink, which some packages need. - - diff --git a/chapter05/gcc-inst.xml b/chapter05/gcc-inst.xml index cc3d011f7..1de7f2a99 100644 --- a/chapter05/gcc-inst.xml +++ b/chapter05/gcc-inst.xml @@ -1,3 +1,5 @@ +   + Installation of GCC @@ -11,17 +13,92 @@ that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building GCC. You have been warned. -Install GCC by running the following commands: +It is recommended by the GCC installation documentation to build +GCC outside of the source directory in a dedicated directory: + +mkdir ../gcc-build +cd ../gcc-build + +Prepare GCC to be compiled: -mkdir ../gcc-build && -cd ../gcc-build && -../gcc-&gcc-version;/configure --prefix=/static \ +../gcc-&gcc-version;/configure --prefix=/static \    --disable-nls --disable-shared \    --with-as=$LFS/static/bin/as \ -   --with-ld=$LFS/static/bin/ld && -make BOOT_LDFLAGS="-static" bootstrap && -make prefix=$LFS/static install-no-fixedincludes && -ln -s gcc $LFS/static/bin/cc +   --with-ld=$LFS/static/bin/ld + +The meaning of the configure options are: + + +--prefix=/static: This is NOT a +typo. GCC hard codes some paths while compiling and so we need to pass +/static as the prefix during the +configure stage. We pass the real install prefix during the installation +stage later on. + +--disable-shared: This prevents the +build of dynamic libraries. They are useless to us at the moment. We'll +create them when we reinstall GCC in chapter 6. + +--with-as=$LFS/static/bin/as and +--with-ld=$LFS/static/bin/ld: GCC can be miscompiled if your +host distribution's Binutils package is quite old. We need a good working +static GCC until we reinstall GCC later in chapter 6. So by using +as and ld from the Binutils +package we compiled earlier in this chapter we ensure that GCC will work +correctly. + + +Continue with compiling the package: + +make BOOT_LDFLAGS="-static" bootstrap + +The meaning of the make options are: + + +BOOT_LDFLAGS="-static": This is +GCC's equivalent to make LDFLAGS="-static" as we use with other packages to +compile them statically. + +bootstrap: The +bootstrap target doesn't just compile GCC, but it +compiles GCC a second time. It uses the first compiled programs to compile +itself a second and third time to make sure the compiler compiled properly +and can compile itself properly. + + +And finish off installing the package: + +make prefix=$LFS/static install-no-fixedincludes + +The meaning of the make option is: + + +install-no-fixedincludes: This prevents +the fixincludes script from running. Preventing this is necessary because +under normal circumstances the GCC installation will run the fixincludes +script which scans your system for header files that need to be fixed. It +might find that the Glibc header files of your host system need to be fixed. +If so, it will fix them and put them in +$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2. Later on +in chapter 6 you will install Glibc which will put its header files in +/usr/include. Next you will install other programs that +use the Glibc headers. GCC will look in +/static/lib/gcc-lib before looking in +/usr/include, with the result of finding and using the +fixed Glibc header files from your host distribution, which are probably +incompatible with the Glibc version actually used on the LFS +system. + + +As the finishing touch we'll create the $LFS/static/bin/cc symlink. A lot of programs +and scripts try to run cc instead of +gcc This is to keep programs generic and usable on +all kinds of Unix systems. Not everybody has GNU CC installed. Just running +cc (C Compiler) leaves the user free to decide which C compiler to install. +The symlink will point to the system's default compiler. + +ln -s gcc $LFS/static/bin/cc diff --git a/chapter05/gcc.xml b/chapter05/gcc.xml index 559009c74..b9b7d52ea 100644 --- a/chapter05/gcc.xml +++ b/chapter05/gcc.xml @@ -5,10 +5,9 @@ Estimated build time: &gcc-time-static; Estimated required disk space: &gcc-compsize-static; -&c5-gcc-inst; -&c5-gcc-exp; -&aa-gcc-desc; +&aa-gcc-shortdesc; &aa-gcc-dep; +&c5-gcc-inst; -- cgit v1.2.3-54-g00ecf