Changeset b3f157c6 for chapter05/glibc.xml

Timestamp:

08/25/2022 07:24:58 AM (20 months ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.2, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

d8c9a43f, e9d65f2f

Parents:

feed7fea

Message:

Don't use dummy.c for glibc sanity check in chap 5

It seems glibc creates dummy.c for its own use. This leaves some
dummy.xxx files in the directory, that may lead some users to think that
the directory is not properly cleaned up after the test (I did :)

So use a pipe so that only a.out is created

File:

• chapter05/glibc.xml (modified) (2 diffs)

chapter05/glibc.xml

@@ -196 +196 @@
       expected. To perform a sanity check, run the following commands:</para>
 
-<screen><userinput>echo 'int main(){}' &gt; dummy.c
-$LFS_TGT-gcc dummy.c
-readelf -l a.out | grep '/ld-linux'</userinput></screen>
+<screen><userinput>echo 'int main(){}' | gcc -xc -
+readelf -l a.out | grep ld-linux</userinput></screen>
 
       <para>If everything is working correctly, there should be no errors,
@@ -213 +212 @@
       continuing on.</para>
 
-      <para>Once all is well, clean up the test files:</para>
-
-<screen><userinput>rm -v dummy.c a.out</userinput></screen>
+      <para>Once all is well, clean up the test file:</para>
+
+<screen><userinput>rm -v a.out</userinput></screen>
 
     </caution>