Changeset ae581da
- Timestamp:
- 08/28/2003 09:19:09 PM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 2ab760c
- Parents:
- 871df54
- Location:
- chapter06
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/binutils-inst.xml
r871df54 rae581da 7 7 Therefore, if you have defined any environment variables that override 8 8 default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting 9 or modifying them when building binutils.</para>9 or modifying them when building Binutils.</para> 10 10 11 11 <para>It is recommended by the Binutils installation documentation to build … … 15 15 cd ../binutils-build</userinput></screen></para> 16 16 17 <para>N ext, prepare Binutils to be compiled:</para>17 <para>Now prepare Binutils for compilation:</para> 18 18 19 19 <para><screen><userinput>../binutils-&binutils-version;/configure \ 20 20 --prefix=/usr --enable-shared</userinput></screen></para> 21 21 22 <para>Co ntinue with compilingthe package:</para>22 <para>Compile the package:</para> 23 23 24 24 <para><screen><userinput>make tooldir=/usr</userinput></screen></para> 25 25 26 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the 27 executables end up) is set to $(exec_prefix)/$(target_alias), which expands 28 into, for example, <filename>/usr/i686-pc-linux-gnu</filename>. Since we only 29 build for our own system, we don't need this target specific directory in 30 <filename>/usr</filename>. That setup would be used if the system was used to 31 cross-compile (for example compiling a package on an Intel machine that 32 generates code that can be executed on PowerPC machines).</para> 33 34 <para>Check the results:</para> 35 26 36 <para><screen><userinput>make check</userinput></screen></para> 27 28 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the29 executables end up) is set to $(exec_prefix)/$(target_alias) which expands30 into, for example, /usr/i686-pc-linux-gnu. Since we only build for our31 own system, we don't need this target specific directory in /usr. That32 setup would be used if the system was used to cross-compile (for example33 compiling a package on the Intel machine that generates code that can be34 executed on Apple PowerPC machines).</para>35 37 36 38 <para>Install the package:</para> … … 38 40 <para><screen><userinput>make tooldir=/usr install</userinput></screen></para> 39 41 42 <para>And remove a library that normally is not meant to be installed on its 43 own:</para> 44 40 45 <para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para> 41 46 -
chapter06/gcc-inst.xml
r871df54 rae581da 10 10 or modifying them when building GCC.</para> 11 11 12 <para>We will be building the C and C++ compilers at this time, so you'll 13 need to unpack both the gcc-core and gcc-g++ tarballs. Other compilers are 14 available in the full gcc package; instructions for building them may be 15 found at <ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para> 12 <para>This time we will build both the C and the C++ compiler, so you'll have 13 to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they 14 will unfold into the same directory. The full GCC package contains even more 15 compilers. Instructions for building these can be found at 16 <ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para> 16 17 17 18 <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch 18 19 patch -Np1 -i ../gcc-&gcc-version;-mmap_test.patch</userinput></screen></para> 19 20 20 <para> It is recommended by the GCC installation documentation to build GCC21 in a dedicated directory outside of the source tree. Create thebuild22 directory :</para>21 <para>GCC's installation documentation recommends to build the package in a 22 dedicated directory separate from the source tree. Create this build 23 directory and go there:</para> 23 24 24 25 <para><screen><userinput>mkdir ../gcc-build 25 26 cd ../gcc-build</userinput></screen></para> 26 27 27 <para> Prepare GCC to be compiled:</para>28 <para>Now prepare GCC for compilation:</para> 28 29 29 30 <para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \ … … 32 33 --enable-languages=c,c++</userinput></screen></para> 33 34 34 <para>The meaning s of the configure options are:</para>35 <para>The meaning of the new configure options:</para> 35 36 36 37 <itemizedlist> … … 51 52 </itemizedlist> 52 53 53 <para>Co ntinue with compilingthe package:</para>54 <para>Compile the package:</para> 54 55 55 56 <para><screen><userinput>make</userinput></screen></para> 56 57 58 <para>Check the results, but don't stop at errors (you'll remember the few 59 known ones):</para> 60 57 61 <para><screen><userinput>make -k check</userinput></screen></para> 58 62 59 <para> Finish installingthe package:</para>63 <para>And install the package:</para> 60 64 61 65 <para><screen><userinput>make install</userinput></screen></para> … … 67 71 <para><screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen></para> 68 72 69 <para>Many packages compile using <emphasis>cc</emphasis> as the name for 70 the C compiler. To satisfy those packages, create a <emphasis>cc</emphasis> 71 symlink:</para> 73 <para>Many packages use the name <userinput>cc</userinput> to call the C 74 compiler. To satisfy those packages, create a symlink:</para> 72 75 73 76 <para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></para> 77 78 <para>Remove the spurious a-out library again:</para> 74 79 75 80 <para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>
Note:
See TracChangeset
for help on using the changeset viewer.