%general-entities; ]> gcc-pass1 &gcc-version;

&gcc-url;

GCC tools, pass 1 GCC requires the GMP, MPFR and MPC packages. As these packages may not be included in your host distribution, they will be built with GCC. Unpack each package into the GCC source directory and rename the resulting directories so the GCC build procedures will automatically use them: There are frequent misunderstandings about this chapter. The procedures are the same as every other chapter, as explained earlier (). First, extract the gcc-&gcc-version; tarball from the sources directory, and then change to the directory created. Only then should you proceed with the instructions below. tar -xf ../mpfr-&mpfr-version;.tar.xz mv -v mpfr-&mpfr-version; mpfr tar -xf ../gmp-&gmp-version;.tar.xz mv -v gmp-&gmp-version; gmp tar -xf ../mpc-&mpc-version;.tar.gz mv -v mpc-&mpc-version; mpc On ARM64 hosts, set the default directory name for 64-bit libraries to lib: sed -e '/lp64=/s/lib64/lib/' \ -i.orig gcc/config/aarch64/t-aarch64-linux The GCC documentation recommends building GCC in a dedicated build directory: mkdir -v build cd build Prepare GCC for compilation: ../configure \ --target=$LFS_TGT \ --prefix=$LFS/tools \ --with-glibc-version=&glibc-version; \ --with-sysroot=$LFS \ --with-newlib \ --without-headers \ --enable-default-pie \ --enable-default-ssp \ --disable-nls \ --disable-shared \ --disable-multilib \ --disable-threads \ --disable-libatomic \ --disable-libgomp \ --disable-libquadmath \ --disable-libssp \ --disable-libvtv \ --disable-libstdcxx \ --enable-languages=c,c++ --with-glibc-version=&glibc-version; This option specifies the version of Glibc which will be used on the target. It is not relevant to the libc of the host distro because everything compiled by pass1 GCC will run in the chroot environment, which is isolated from libc of the host distro. --with-newlib Since a working C library is not yet available, this ensures that the inhibit_libc constant is defined when building libgcc. This prevents the compiling of any code that requires libc support. --without-headers When creating a complete cross-compiler, GCC requires standard headers compatible with the target system. For our purposes these headers will not be needed. This switch prevents GCC from looking for them. --enable-default-pie and --enable-default-ssp Those switches allow GCC to compile programs with some hardening security features (more information on those in the in chapter 8) by default. The are not strictly needed at this stage, since the compiler will only produce temporary executables. But it is cleaner to have the temporary packages be as close as possible to the final ones. --disable-shared This switch forces GCC to link its internal libraries statically. We need this because the shared libraries require Glibc, which is not yet installed on the target system. --disable-multilib On ARM64, LFS does not support a multilib configuration. --disable-decimal-float, --disable-threads, --disable-libatomic, --disable-libgomp, --disable-libquadmath, --disable-libssp, --disable-libvtv, --disable-libstdcxx These switches disable support for the decimal floating point extension, threading, libatomic, libgomp, libquadmath, libssp, libvtv, and the C++ standard library respectively. These features will fail to compile when building a cross-compiler and are not necessary for the task of cross-compiling the temporary libc. --enable-languages=c,c++ This option ensures that only the C and C++ compilers are built. These are the only languages needed now. Compile GCC by running: make Install the package: make install This build of GCC has installed a couple of internal system headers. Normally one of them, limits.h, would in turn include the corresponding system limits.h header, in this case, $LFS/usr/include/limits.h. However, at the time of this build of GCC $LFS/usr/include/limits.h does not exist, so the internal header that has just been installed is a partial, self-contained file and does not include the extended features of the system header. This is adequate for building Glibc, but the full internal header will be needed later. Create a full version of the internal header using a command that is identical to what the GCC build system does in normal circumstances: cd .. cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \ `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/install-tools/include/limits.h