diff options
author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2020-06-12 04:40:07 +0000 |
---|---|---|
committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2020-06-12 04:40:07 +0000 |
commit | 6a156bab1b41dfcbebcf69325dff81b73a2afad7 (patch) | |
tree | 39451253ebce7058ff7282090bd572ac36dff998 /chapter08/adjusting.xml | |
parent | ea7ec72fba2b9749da2c22db67152eccaef5dfb0 (diff) |
Mostly text updates in Chapter 8.
There are a couple of minor command changes.
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11924 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter08/adjusting.xml')
-rw-r--r-- | chapter08/adjusting.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/chapter08/adjusting.xml b/chapter08/adjusting.xml index 3e6b49e19..4bd8a85cc 100644 --- a/chapter08/adjusting.xml +++ b/chapter08/adjusting.xml @@ -50,7 +50,7 @@ readelf -l a.out | grep ': /lib'</userinput></screen> <para os="b">There should be no errors, and the output of the last command will be (allowing for - platform-specific differences in dynamic linker name):</para> + platform-specific differences in the dynamic linker name):</para> <screen os="c"><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen> @@ -104,7 +104,7 @@ SEARCH_DIR("/lib")</computeroutput></screen> <screen os="o"><computeroutput>attempt to open /lib/libc.so.6 succeeded</computeroutput></screen> - <para os="p">Lastly, make sure GCC is using the correct dynamic linker:</para> + <para os="p">Make sure GCC is using the correct dynamic linker:</para> <screen os="q"><userinput>grep found dummy.log</userinput></screen> @@ -115,8 +115,8 @@ SEARCH_DIR("/lib")</computeroutput></screen> <para os="t">If the output does not appear as shown above or is not received at all, then something is seriously wrong. Investigate and retrace the - steps to find out where the problem is and correct it. The most likely - reason is that something went wrong with the specs file adjustment. Any + steps to find out where the problem is and correct it. <!--The most likely + reason is that something went wrong with the specs file adjustment.--> Any issues will need to be resolved before continuing with the process.</para> <para os="u">Once everything is working correctly, clean up the test files:</para> |