- Timestamp:
- 01/17/2004 07:53:07 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, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 0afaac4
- Parents:
- 443cace
- Location:
- chapter05
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/chapter05.xml
r443cace r51fe215 463 463 464 464 <para>We recommend that you cut-and-paste the above rather than try and type it 465 all in. Or you can edit the specs file by hand if you want to: just replace any 466 occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2".</para> 465 all in. Or you can edit the specs file by hand if you want to: just replace the 466 occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2". Be sure to 467 visually inspect the specs file to verify the intended change was actually 468 made.</para> 467 469 468 470 <important><para>If you are working on a platform where the name of the dynamic … … 488 490 489 491 <screen><userinput>echo 'main(){}' > dummy.c 490 gcc dummy.c492 cc dummy.c 491 493 readelf -l a.out | grep ': /tools'</userinput></screen> 492 494 … … 496 498 <blockquote><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</screen></blockquote> 497 499 498 <para>If you did not receive the output as shown above, or received no output at 499 all, then something is seriously wrong. You will need to investigate and retrace 500 your steps to find out where the problem is and correct it. There is no point in 501 continuing until this is done. Most likely something went wrong with the specs 502 file amendment above. Note especially that <filename>/tools/lib</filename> 503 appears as the prefix of our dynamic linker. Of course, if you are working on a 504 platform where the name of the dynamic linker is something other than 505 <filename>ld-linux.so.2</filename>, then the output will be slightly 506 different.</para> 500 <para>(Of course allowing for platform specific differences in dynamic linker 501 name). Note especially that <filename class="directory">/tools/lib</filename> 502 appears as the prefix of our dynamic linker. If you did not receive the output 503 as shown above, or received no output at all, then something is seriously wrong. 504 You will need to investigate and retrace your steps to find out where the 505 problem is and correct it. There is no point in continuing until this is done. 506 First, redo the sanity check using <userinput>gcc</userinput> instead of 507 <userinput>cc</userinput>. If this works it means the 508 <filename class="symlink">/tools/bin/cc</filename> symlink is missing. Revisit 509 <xref linkend="ch05-gcc-pass1"/> and fix the symlink. Second, ensure your $PATH 510 is correct. You can check this by running <userinput>echo $PATH</userinput> and 511 verifying that <filename class="directory">/tools/bin</filename> is at the head 512 of the list. If the $PATH is wrong it could mean you're not logged in as user 513 <emphasis>lfs</emphasis> or something went wrong back in 514 <xref linkend="ch05-settingenviron"/>. Third, something may have gone wrong with 515 the specs file amendment above. In this case redo the specs file amendment 516 ensuring to cut-and-paste the commands as was recommended.</para> 507 517 508 518 <para>Once you are satisfied that all is well, clean up the test files:</para> -
chapter05/gcc-pass1.xml
r443cace r51fe215 99 99 C compiler to install, as long as there's a symlink pointing to it:</para> 100 100 101 <screen><userinput>ln -s fgcc /tools/bin/cc</userinput></screen>101 <screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen> 102 102 103 103 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.