gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-08-03 01:55:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

instead of sed'ing the config.make file, create a configparms file with

Browse Source 
'cross-compiling = no' as contents


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1524 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2002-02-01 19:23:54 +00:00
parent a193394081
commit 94cb444490
2 changed files with 8 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
chapter06/glibc-exp.xml
View File

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

4
chapter06/glibc-inst.xml
View File

@ -29,9 +29,7 @@ mkdir ../glibc-build &amp;&amp;
cd ../glibc-build &amp;&amp; cd ../glibc-build &amp;&amp;
../glibc-&glibc-version;/configure --prefix=/usr \ ../glibc-&glibc-version;/configure --prefix=/usr \
&nbsp;&nbsp;&nbsp;--enable-add-ons --libexecdir=/usr/bin &amp;&amp; &nbsp;&nbsp;&nbsp;--enable-add-ons --libexecdir=/usr/bin &amp;&amp;
cp config.make config.make.backup &amp;&amp; echo "cross-compiling = no" &gt; configparms &amp;&amp;
sed 's/cross-compiling = yes/cross-compiling = no/' \
&nbsp;&nbsp;&nbsp;config.make.backup &gt; config.make &amp;&amp;
make &amp;&amp; make &amp;&amp;
make install &amp;&amp; make install &amp;&amp;
make localedata/install-locales &amp;&amp; make localedata/install-locales &amp;&amp;