Changeset 51fe215


Ignore:
Timestamp:
01/17/2004 07:53:07 AM (20 years ago)
Author:
Greg Schafer <greg@…>
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
Message:

Expanded the Locking in Glibc and Re-adjusting the toolchain
sections to also catch missing cc->gcc symlink and provide more
help for when things go wrong.

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

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    r443cace r51fe215  
    5151</listitem>
    5252
     53<listitem><para>January 16th, 2004 [greg]: Expanded the Locking in Glibc and
     54Re-adjusting the toolchain sections to also catch missing cc->gcc symlink and
     55provide more help for when things go wrong.</para></listitem>
     56
    5357<listitem><para>January 16th, 2004 [greg]: Implemented changes to make the
    5458running of the Chapter 5 test suites strictly optional i.e. the default action

  • chapter05/chapter05.xml

    r443cace r51fe215  
    463463
    464464<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>
     465all in. Or you can edit the specs file by hand if you want to: just replace the
     466occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2". Be sure to
     467visually inspect the specs file to verify the intended change was actually
     468made.</para>
    467469
    468470<important><para>If you are working on a platform where the name of the dynamic
    … …  
    488490
    489491<screen><userinput>echo 'main(){}' &gt; dummy.c
    490 gcc dummy.c
     492cc dummy.c
    491493readelf -l a.out | grep ': /tools'</userinput></screen>
    492494
    … …  
    496498<blockquote><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</screen></blockquote>
    497499
    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
     501name). Note especially that <filename class="directory">/tools/lib</filename>
     502appears as the prefix of our dynamic linker. If you did not receive the output
     503as shown above, or received no output at all, then something is seriously wrong.
     504You will need to investigate and retrace your steps to find out where the
     505problem is and correct it. There is no point in continuing until this is done.
     506First, 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
     510is correct. You can check this by running <userinput>echo $PATH</userinput> and
     511verifying that <filename class="directory">/tools/bin</filename> is at the head
     512of 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
     515the specs file amendment above. In this case redo the specs file amendment
     516ensuring to cut-and-paste the commands as was recommended.</para>
    507517
    508518<para>Once you are satisfied that all is well, clean up the test files:</para>

  • chapter05/gcc-pass1.xml

    r443cace r51fe215  
    9999C compiler to install, as long as there's a symlink pointing to it:</para>
    100100
    101 <screen><userinput>ln -sf gcc /tools/bin/cc</userinput></screen>
     101<screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
    102102
    103103</sect2>

  • chapter06/chapter06.xml

    r443cace r51fe215  
    364364
    365365<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 intended
    367 changes were actually made.</para>
     366before, it is a good idea to visually inspect the specs file to verify the
     367intended change was actually made.</para>
    368368
    369369<important><para>If you are working on a platform where the name of the dynamic
    … …  
    381381
    382382<screen><userinput>echo 'main(){}' &gt; dummy.c
    383 gcc dummy.c
     383cc dummy.c
    384384readelf -l a.out | grep ': /lib'</userinput></screen>
    385385
    … …  
    389389<blockquote><screen>[Requesting program interpreter: /lib/ld-linux.so.2]</screen></blockquote>
    390390
    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
     392name). Note especially that <filename class="directory">/lib</filename> now
     393appears as the prefix of our dynamic linker. If you did not receive the output
     394as shown above, or received no output at all, then something is seriously wrong.
     395You will need to investigate and retrace your steps to find out where the
     396problem is and correct it. There is no point in continuing until this is done.
     397Most likely something went wrong with the specs file amendment above.</para>
    400398
    401399<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.