Changeset d1391f0


Ignore:
Timestamp:
09/17/2003 09:57:52 AM (21 years ago)
Author:
Greg Schafer <greg@…>
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:
e2bd9bf
Parents:
b920e40
Message:

Do "make -C ld install" instead of "make -C ld install-data-local" to install a whole new linker instead of just the new ldscripts.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2831 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
5 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    rb920e40 rd1391f0  
    9595</para></listitem>
    9696
     97<listitem><para>September 17th, 2003 [greg]: Chapters 5 and 6 - Locking in
     98Glibc and Re-adjusting the toolchain: Do "make -C ld install" instead of "make
     99-C ld install-data-local" to install a whole new linker instead of just the
     100new ldscripts.</para></listitem>
     101
    97102<listitem><para>September 16th, 2003 [greg]: Chapters 5 and 6 - Locking in
    98103Glibc and Re-adjusting the toolchain: Added sanity checks.</para></listitem>

  • chapter05/lockingglibc.xml

    rb920e40 rd1391f0  
    55<para>Now that the temporary C libraries have been installed, we want all
    66the tools compiled in the rest of this chapter to be linked against these
    7 libraries. To accomplish this, we need to adjust the linker's scripts and the
    8 compiler's specs file.</para>
     7libraries. To accomplish this, we need to adjust the linker and the compiler's
     8specs file.</para>
    99
    10 <para>First install the adjusted linker scripts by running the following from
    11 within the <filename class="directory">binutils-build</filename>
    12 directory:</para>
     10<para>First install the adjusted linker by running the following from within
     11the <filename class="directory">binutils-build</filename> directory:</para>
    1312
    14 <para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
     13<para><screen><userinput>make -C ld install</userinput></screen></para>
    1514
    16 <para>These scripts were adjusted a little while back, at the end of the first
    17 pass of Binutils, and contain no mention of <filename>/lib</filename>,
    18 <filename>/usr/lib</filename> or <filename>/usr/local/lib</filename>.
    19 From this point onwards everything will link <emphasis>only</emphasis>
    20 against the libraries in <filename>/tools/lib</filename>.</para>
     15<para>The linker was adjusted a little while back, at the end of the first
     16pass of Binutils. From this point onwards everything will link <emphasis>only
     17</emphasis> against the libraries in <filename>/tools/lib</filename>.</para>
    2118
    22 <para>Now that the scripts are adjusted, you have to remove the Binutils
    23 build and source directories.</para>
     19<para>Now that the adjusted linker is installed, you have to remove the
     20Binutils build and source directories.</para>
    2421
    2522<para>The next thing to do is to amend our GCC specs file so that it points

  • chapter06/adjustingtoolchain.xml

    rb920e40 rd1391f0  
    88in the "Locking in" stage in the beginning of the previous chapter.</para>
    99
    10 <para>The first thing to do is to adjust the linker scripts. For this we
    11 retained the source and build directories from the second pass over Binutils.
    12 Install the adjusted linker scripts by running the following from within the
     10<para>The first thing to do is to adjust the linker. For this we retained the
     11source and build directories from the second pass over Binutils. Install the
     12adjusted linker by running the following from within the
    1313<filename class="directory">binutils-build</filename> directory:</para>
    1414
    15 <para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
     15<para><screen><userinput>make -C ld install</userinput></screen></para>
    1616
    17 <para>The linker scripts now contain
    18 no mention of <filename class="directory">/tools/lib</filename> anymore.
    19 From now on every compiled program will link <emphasis>only</emphasis>
    20 against the libraries in <filename>/usr/lib</filename> and
    21 <filename>/lib</filename>.</para>
     17<para>From now on every compiled program will link <emphasis>only</emphasis>
     18against the libraries in <filename>/usr/lib</filename> and <filename>/lib
     19</filename>.</para>
    2220
    2321<para>You can now remove the Binutils source and build directories.</para>
    … …  
    3533
    3634<para>Again, cutting and pasting the above is recommended. And just like
    37 before, it is a good idea to check the linker scripts and the specs file to
    38 ensure the intended changes were actually made.</para>
    39 
    40 <para>Note that the linker scripts will still contain a reference to
    41 <filename class="directory">/tools/i686-pc-linux-gnu/lib</filename>. This
    42 is unavoidable, but luckily does not present a problem. There are no
    43 libraries in that location as all the temporary tools libraries are
    44 located in <filename class="directory">/tools/lib</filename>.</para>
     35before, it is a good idea to check the specs file to ensure the intended
     36changes were actually made.</para>
    4537
    4638<caution><para>It is imperative at this point to stop and ensure that the

  • chapter06/glibc-inst.xml

    rb920e40 rd1391f0  
    55
    66<para>The Glibc build system is very well self-contained and will install
    7 perfectly, even though our compiler specs file and linker scripts are still
    8 pointing at <filename>/tools</filename>. We cannot adjust the specs and
    9 ldscripts before the Glibc install, because the Glibc autoconf tests would then
    10 give bogus results and thus defeat our goal of achieving a clean build.</para>
     7perfectly, even though our compiler specs file and linker are still pointing
     8at <filename>/tools</filename>. We cannot adjust the specs and linker before
     9the Glibc install, because the Glibc autoconf tests would then give bogus
     10results and thus defeat our goal of achieving a clean build.</para>
    1111
    1212<note><para>The testsuite for Glibc in this chapter is considered <emphasis>

  • index.xml

    rb920e40 rd1391f0  
    44
    55
    6 <!ENTITY version "20030916">
    7 <!ENTITY releasedate "September 16th, 2003">
     6<!ENTITY version "20030917">
     7<!ENTITY releasedate "September 17th, 2003">
    88<!ENTITY nbsp " ">
    99
Note: See TracChangeset for help on using the changeset viewer.