Changeset 51fe215 for chapter06/chapter06.xml
- Timestamp:
- 01/17/2004 07:53:07 AM (20 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_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:
- 0afaac4
- Parents:
- 443cace
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/chapter06.xml
r443cace r51fe215 364 364 365 365 <para>Again, cutting and pasting the above is recommended. And just like 366 before, it is a good idea to check the specs file to ensure the intended367 changes wereactually made.</para>366 before, it is a good idea to visually inspect the specs file to verify the 367 intended change was actually made.</para> 368 368 369 369 <important><para>If you are working on a platform where the name of the dynamic … … 381 381 382 382 <screen><userinput>echo 'main(){}' > dummy.c 383 gcc dummy.c383 cc dummy.c 384 384 readelf -l a.out | grep ': /lib'</userinput></screen> 385 385 … … 389 389 <blockquote><screen>[Requesting program interpreter: /lib/ld-linux.so.2]</screen></blockquote> 390 390 391 <para>If you did not receive the output as shown above, or received no output at 392 all, then something is seriously wrong. You will need to investigate and retrace 393 your steps to find out where the problem is and correct it. There is no point in 394 continuing until this is done. Most likely something went wrong with the specs 395 file amendment above. Note especially that <filename>/lib</filename> now appears 396 as the prefix of our dynamic linker. Of course, if you are working on a platform 397 where the name of the dynamic linker is something other than 398 <filename>ld-linux.so.2</filename>, then the output will be slightly 399 different.</para> 391 <para>(Of course allowing for platform specific differences in dynamic linker 392 name). Note especially that <filename class="directory">/lib</filename> now 393 appears as the prefix of our dynamic linker. If you did not receive the output 394 as shown above, or received no output at all, then something is seriously wrong. 395 You will need to investigate and retrace your steps to find out where the 396 problem is and correct it. There is no point in continuing until this is done. 397 Most likely something went wrong with the specs file amendment above.</para> 400 398 401 399 <para>Once you are satisfied that all is well, clean up the test files:</para>
Note:
See TracChangeset
for help on using the changeset viewer.