|
@@ -33,17 +33,13 @@ we install with Glibc: linuxthreads</para>
|
|
|
<para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
|
|
|
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 > 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" > 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
|
|
|
start a new bash shell which will replace the current shell. This is
|