Changeset 94cb4444 for chapter06/glibc-exp.xml

Timestamp:

02/01/2002 07:23:54 PM (22 years ago)

Author:

Gerard Beekmans <gerard@…>

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, v3_2, v3_3, v4_0, v4_1, 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:

4762fcc

Parents:

a193394

Message:

instead of sed'ing the config.make file, create a configparms file with
'cross-compiling = no' as contents

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

File:

• chapter06/glibc-exp.xml (modified) (1 diff)

chapter06/glibc-exp.xml

@@ -34 +34 @@
 pt_chown program to be installed in the /usr/bin directory.</para>
 
-<para><userinput>sed 's/cross-compiling = yes/cross-compiling = no/'
-config.make.backup &gt; config.make:</userinput> This time, sed searches
-through <filename>config.make.backup</filename> and replaces all occurences
-of <filename>cross-compiling = yes</filename> with
-<filename>cross-compiling = no</filename>. We do this because we are
-only building for our own system. Cross-compiling is used, for instance,
-to build a package for an Apple Power PC on an Intel system. The reason
-Glibc thinks we're cross-compiling is that it can't compile a test program
-to determine this, so it automatically defaults to a cross-compiler.
-Compiling the test program failes because Glibc hasn't been installed
-yet.</para>
+<para><userinput>echo "cross-compiling = no" &gt; configparms:</userinput>
+We do this because we are only building for our own system. Cross-compiling
+is used, for instance, to build a package for an Apple Power PC on an
+Intel system. The reason Glibc thinks we're cross-compiling is that it
+can't compile a test program to determine this, so it automatically defaults
+to a cross-compiler. Compiling the test program failes because Glibc hasn't
+been installed yet.</para>
 
 <para><userinput>exec /bin/bash:</userinput>This command will