Changeset 6267e8e
- Timestamp:
- 10/08/2003 04:49:02 AM (21 years ago)
- Branches:
- 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, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 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, v5_0, v5_1, v5_1_1, 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
- Children:
- 2723b39
- Parents:
- 76b9eb4
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/lockingglibc.xml
r76b9eb4 r6267e8e 60 60 <blockquote><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</screen></blockquote> 61 61 62 <para>If you did not receive the output as shown above, then something is 63 seriously wrong. This includes if the output of the command is blank! 64 You will need to investigate and retrace your steps to find 65 out where the problem is and correct it. There is no point in continuing 66 until this is done. Most likely something went wrong with the specs file 67 amendment above. Note especially that <filename>/tools/lib</filename> appears 68 as the prefix of our dynamic linker. Of course, if you are working on a 62 <para>If you did not receive the output as shown above, or received no output at 63 all, then something is seriously wrong. You will need to investigate and retrace 64 your steps to find out where the problem is and correct it. There is no point in 65 continuing until this is done. Most likely something went wrong with the specs 66 file amendment above. Note especially that <filename>/tools/lib</filename> 67 appears as the prefix of our dynamic linker. Of course, if you are working on a 69 68 platform where the name of the dynamic linker is something other than 70 <filename>ld-linux.so.2</filename>, then the output will be slightly different.71 </para>69 <filename>ld-linux.so.2</filename>, then the output will be slightly 70 different.</para> 72 71 73 72 <para>Once you are satisfied that all is well, clean up the test files:</para> -
chapter06/adjustingtoolchain.xml
r76b9eb4 r6267e8e 70 70 <blockquote><screen>[Requesting program interpreter: /lib/ld-linux.so.2]</screen></blockquote> 71 71 72 <para>If you did not receive the output as shown above, then something is 73 seriously wrong. This includes the output of the above command being empty! 74 You will need to investigate and retrace your steps to find 75 out where the problem is and correct it. There is no point in continuing 76 until this is done. Most likely something went wrong with the specs file 77 amendment above. Note especially that <filename>/lib</filename> now appears as 78 the prefix of our dynamic linker. Of course, if you are working on a platform 72 <para>If you did not receive the output as shown above, or received no output at 73 all, then something is seriously wrong. You will need to investigate and retrace 74 your steps to find out where the problem is and correct it. There is no point in 75 continuing until this is done. Most likely something went wrong with the specs 76 file amendment above. Note especially that <filename>/lib</filename> now appears 77 as the prefix of our dynamic linker. Of course, if you are working on a platform 79 78 where the name of the dynamic linker is something other than 80 79 <filename>ld-linux.so.2</filename>, then the output will be slightly
Note:
See TracChangeset
for help on using the changeset viewer.