[519ee45] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
| 7 |
|
---|
| 8 | <sect1 id="ch-system-readjusting">
|
---|
| 9 | <?dbhtml filename="readjusting.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Re-adjusting the Toolchain</title>
|
---|
| 12 |
|
---|
| 13 | <para>Now that the final C libraries have been installed, it is time to adjust
|
---|
| 14 | the toolchain again. The toolchain will be adjusted so that it will link any
|
---|
| 15 | newly compiled program against these new libraries. This is a similar process
|
---|
| 16 | used in the <quote>Adjusting</quote> phase in the beginning of <xref
|
---|
| 17 | linkend="chapter-temporary-tools"/>, but with the adjustments reversed. In <xref
|
---|
| 18 | linkend="chapter-temporary-tools"/>, the chain was guided from the host's
|
---|
| 19 | <filename class="directory">/{,usr/}lib</filename> directories to the new
|
---|
| 20 | <filename class="directory">/tools/lib</filename> directory. Now, the chain will
|
---|
| 21 | be guided from that same <filename class="directory">/tools/lib</filename>
|
---|
| 22 | directory to the LFS <filename class="directory">/{,usr/}lib</filename>
|
---|
| 23 | directories.</para>
|
---|
| 24 |
|
---|
| 25 | <para>First, backup the <filename class="directory">/tools</filename> linker,
|
---|
| 26 | and replace it with the adjusted linker we made in chapter 5. We'll also create
|
---|
| 27 | a link to its counterpart in <filename class="directory">/tools/$(gcc
|
---|
| 28 | -dumpmachine)/bin</filename>.</para>
|
---|
| 29 |
|
---|
| 30 | <screen><userinput>mv -v /tools/bin/{ld,ld-old}
|
---|
| 31 | mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
|
---|
| 32 | mv -v /tools/bin/{ld-new,ld}
|
---|
| 33 | ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen>
|
---|
| 34 |
|
---|
| 35 | <para>Next, amend the GCC specs file so that it points to the new
|
---|
| 36 | dynamic linker, and so that GCC knows where to find its start files.
|
---|
| 37 | A <command>perl</command> command accomplishes this:</para>
|
---|
| 38 |
|
---|
| 39 | <screen><userinput>gcc -dumpspecs | \
|
---|
| 40 | perl -p -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g;' \
|
---|
| 41 | -e 's@\*startfile_prefix_spec:\n@$_/usr/lib/ @g;' > \
|
---|
| 42 | `dirname $(gcc --print-libgcc-file-name)`/specs</userinput></screen>
|
---|
| 43 |
|
---|
| 44 | <para>It is a good idea to visually inspect the specs file to verify the
|
---|
| 45 | intended change was actually made.</para>
|
---|
| 46 |
|
---|
| 47 | <important>
|
---|
| 48 | <para>If working on a platform where the name of the dynamic linker is
|
---|
| 49 | something other than <filename class="libraryfile">ld-linux.so.2</filename>,
|
---|
| 50 | substitute <quote>ld-linux.so.2</quote> with the name of the platform's
|
---|
| 51 | dynamic linker in the above commands. Refer back to <xref
|
---|
| 52 | linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
|
---|
| 53 | </important>
|
---|
| 54 |
|
---|
| 55 | <para>It is imperative at this point to ensure that the basic
|
---|
| 56 | functions (compiling and linking) of the adjusted toolchain are working
|
---|
| 57 | as expected. To do this, perform the following sanity checks:</para>
|
---|
| 58 |
|
---|
| 59 | <screen role="nodump" os="a"><userinput>echo 'main(){}' > dummy.c
|
---|
| 60 | cc dummy.c -Wl,--verbose &> dummy.log
|
---|
| 61 | readelf -l a.out | grep ': /lib'</userinput></screen>
|
---|
| 62 |
|
---|
| 63 | <para os="b">If everything is working correctly, there should be no errors,
|
---|
| 64 | and the output of the last command will be (allowing for
|
---|
| 65 | platform-specific differences in dynamic linker name):</para>
|
---|
| 66 |
|
---|
| 67 | <screen os="c"><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
|
---|
| 68 |
|
---|
| 69 | <para>Note that <filename class="directory">/lib</filename> is now
|
---|
| 70 | the prefix of our dynamic linker.</para>
|
---|
| 71 |
|
---|
| 72 | <para os="d">Now make sure that we're setup to use the correct startfiles:</para>
|
---|
| 73 |
|
---|
| 74 | <screen role="nodump" os="e"><userinput>grep -o '/usr/lib.*/crt[1in].* .*' dummy.log</userinput></screen>
|
---|
| 75 |
|
---|
| 76 | <para os="f">If everything is working correctly, there should be no errors,
|
---|
| 77 | and the output of the last command will be:</para>
|
---|
| 78 |
|
---|
| 79 | <screen><computeroutput>/usr/lib/crt1.o succeeded
|
---|
| 80 | /usr/lib/crti.o succeeded
|
---|
| 81 | /usr/lib/crtn.o succeeded</computeroutput></screen>
|
---|
| 82 |
|
---|
| 83 | <para os="g">Next, verify that the new linker is being used with the correct search paths:</para>
|
---|
| 84 |
|
---|
| 85 | <screen role="nodump" os="h"><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'</userinput></screen>
|
---|
| 86 |
|
---|
| 87 | <para os="i">If everything is working correctly, there should be no errors,
|
---|
| 88 | and the output of the last command will be:</para>
|
---|
| 89 |
|
---|
| 90 | <screen><computeroutput>SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
|
---|
| 91 | SEARCH_DIR("/usr/lib")
|
---|
| 92 | SEARCH_DIR("/lib");</computeroutput></screen>
|
---|
| 93 |
|
---|
| 94 | <para os="j">Next make sure that we're using the correct libc:</para>
|
---|
| 95 |
|
---|
| 96 | <screen role="nodump" os="k"><userinput>grep "/lib/libc.so.6 " dummy.log</userinput></screen>
|
---|
| 97 |
|
---|
| 98 | <para os="l">If everything is working correctly, there should be no errors,
|
---|
| 99 | and the output of the last command will be:</para>
|
---|
| 100 |
|
---|
| 101 | <screen os="m"><computeroutput>attempt to open /lib/libc.so.6 succeeded</computeroutput></screen>
|
---|
| 102 |
|
---|
| 103 | <para os="n">Lastly, make sure GCC is using the correct dynamic linker:</para>
|
---|
| 104 |
|
---|
| 105 | <screen role="nodump" os="o"><userinput>grep found dummy.log</userinput></screen>
|
---|
| 106 |
|
---|
| 107 | <para os="p">If everything is working correctly, there should be no errors,
|
---|
| 108 | and the output of the last command will be (allowing for
|
---|
| 109 | platform-specific differences in dynamic linker name):</para>
|
---|
| 110 |
|
---|
| 111 | <screen os="q"><computeroutput>found ld-linux.so.2 at /lib/ld-linux.so.2</computeroutput></screen>
|
---|
| 112 |
|
---|
| 113 | <para os="r">If the output does not appear as shown above or is not received
|
---|
| 114 | at all, then something is seriously wrong. Investigate and retrace the
|
---|
| 115 | steps to find out where the problem is and correct it. The most likely
|
---|
| 116 | reason is that something went wrong with the specs file adjustment. Any
|
---|
| 117 | issues will need to be resolved before continuing on with the process.</para>
|
---|
| 118 |
|
---|
| 119 | <para os="s">Once everything is working correctly, clean up the test files:</para>
|
---|
| 120 |
|
---|
| 121 | <screen role="nodump" os="t"><userinput>rm -v dummy.c a.out dummy.log</userinput></screen>
|
---|
| 122 |
|
---|
| 123 | </sect1>
|
---|