- Timestamp:
- 02/02/2006 09:35:05 PM (18 years ago)
- Children:
- a7fe252
- Parents:
- 0e5c784
- Location:
- chapter05
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/adjusting.xml
r0e5c784 r9e26f63 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 -
chapter05/bash.xml
r0e5c784 r9e26f63 47 47 48 48 <variablelist> 49 <title>The meaning of the configure option s:</title>49 <title>The meaning of the configure option:</title> 50 50 51 51 <varlistentry> 52 52 <term><parameter>--without-bash-malloc</parameter></term> 53 53 <listitem> 54 <para>This option sturns off the use of Bash's memory allocation54 <para>This option turns off the use of Bash's memory allocation 55 55 (<function>malloc</function>) function which is known to cause 56 56 segmentation faults. By turning this option off, Bash will use -
chapter05/binutils-pass1.xml
r0e5c784 r9e26f63 106 106 107 107 <screen><userinput>make -C ld clean 108 make -C ld LIB_PATH=/tools/lib</userinput></screen> 108 make -C ld LIB_PATH=/tools/lib 109 cp -v ld/ld-new /tools/bin</userinput></screen> 109 110 110 111 <variablelist> … … 135 136 </variablelist> 136 137 137 <warning>138 <para><emphasis>Do not</emphasis> remove the Binutils build and source139 directories yet. These will be needed again in their current state later140 in this chapter.</para>141 </warning>142 143 138 </sect2> 144 139 -
chapter05/binutils-pass2.xml
r0e5c784 r9e26f63 87 87 88 88 <screen><userinput>make -C ld clean 89 make -C ld L DFLAGS="-s" LIB_PATH=/usr/lib:/lib89 make -C ld LIB_PATH=/usr/lib:/lib 90 90 cp -v ld/ld-new /tools/bin</userinput></screen> 91 91 -
chapter05/gcc-pass1.xml
r0e5c784 r9e26f63 94 94 95 95 <variablelist> 96 <title>The meaning of the make parameter s:</title>96 <title>The meaning of the make parameter:</title> 97 97 98 98 <varlistentry> -
chapter05/gettext.xml
r0e5c784 r9e26f63 51 51 52 52 <variablelist> 53 <title>The meaning of the configure option s:</title>53 <title>The meaning of the configure option:</title> 54 54 55 55 <varlistentry> -
chapter05/grep.xml
r0e5c784 r9e26f63 48 48 49 49 <variablelist> 50 <title>The meaning of the configure option s:</title>50 <title>The meaning of the configure option:</title> 51 51 52 52 <varlistentry> -
chapter05/introduction.xml
r0e5c784 r9e26f63 53 53 <para>After installing each package, delete its source and build directories, 54 54 unless specifically instructed otherwise. Deleting the sources prevents 55 mis-configuration when the same package is reinstalled later. Only three 56 of the packages need to retain the source and build directories in order 57 for their contents to be used by later commands. Pay special attention to 58 these reminders.</para> 55 mis-configuration when the same package is reinstalled later.</para> 59 56 </important> 60 57
Note:
See TracChangeset
for help on using the changeset viewer.