source: chapter06/adjusting.xml@ 6a0d235

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 7.7 7.8 7.9 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 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
Last change on this file since 6a0d235 was 6a0d235, checked in by Bruce Dubbs <bdubbs@…>, 9 years ago

Clarify output in Chapter 6 adjusting section

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

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