Changeset e6ab4b5 for chapter05/adjusting.xml
- Timestamp:
- 02/03/2006 06:23:22 PM (18 years ago)
- Children:
- fa994c9
- Parents:
- b4cd3c5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/adjusting.xml
rb4cd3c5 re6ab4b5 16 16 compiler's specs file need to be adjusted.</para> 17 17 18 <para>The linker, adjusted at the end of the first pass of Binutils, 19 is installed by running the following command from within the 20 <filename class="directory">binutils-build</filename> directory:</para> 18 <para>The linker, adjusted at the end of the first pass of Binutils, needs 19 to be renamed so that it can be properly found and used. First, backup the 20 original linker, then replace it with the adjusted linker. We'll also 21 create a link to its counterpart in <filename class="directory"> 22 /tools/$(gcc -dumpmachine)/bin</filename></para> 21 23 22 <screen><userinput>make -C ld install</userinput></screen> 24 <screen><userinput>mv -v /tools/bin/{ld,ld-old} 25 mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old} 26 mv -v /tools/bin/{ld-new,ld} 27 ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen> 23 28 24 29 <para>From this point onwards, everything will link only against the 25 30 libraries in <filename class="directory">/tools/lib</filename>.</para> 26 27 <note>28 <para>If the earlier warning to retain the Binutils source and29 build directories from the first pass was missed, ignore the above30 command. This results in a small chance that the subsequent testing31 programs will link against libraries on the host. This is not ideal,32 but it is not a major problem. The situation is corrected when the33 second pass of Binutils is installed later.</para>34 </note>35 36 <para>Now that the adjusted linker is installed, the Binutils build and source37 directories should be removed.</para>38 31 39 32 <para>The next task is to point GCC to the new dynamic linker. This is done by
Note:
See TracChangeset
for help on using the changeset viewer.