cross-ng: gcc: don't rely on "uname -m"

This commit is contained in:
Xi Ruoyao 2021-12-17 20:09:06 +08:00
parent 96dda27a0f
commit 30ae09bb76
No known key found for this signature in database
GPG Key ID: D95E4716CCBB34DC
3 changed files with 19 additions and 23 deletions

View File

@ -62,15 +62,13 @@ mv -v gmp-&gmp-version; gmp
tar -xf ../mpc-&mpc-version;.tar.gz tar -xf ../mpc-&mpc-version;.tar.gz
mv -v mpc-&mpc-version; mpc</userinput></screen> mv -v mpc-&mpc-version; mpc</userinput></screen>
<para>On x86_64 hosts, set the default directory name for <para>For x86_64 target, set the default directory name for
64-bit libraries to <quote>lib</quote>:</para> 64-bit libraries to <quote>lib</quote>. The command is unnecessary,
but harmless for 32-bit x86. If you are building for another target,
you may need to adjust the command for your target.</para>
<screen><userinput remap="pre">case $(uname -m) in <screen><userinput remap="pre">sed -e '/m64=/s/lib64/lib/' \
x86_64) -i.orig gcc/config/i386/t-linux64</userinput></screen>
sed -e '/m64=/s/lib64/lib/' \
-i.orig gcc/config/i386/t-linux64
;;
esac</userinput></screen>
<para>The GCC documentation recommends building GCC <para>The GCC documentation recommends building GCC
in a dedicated build directory:</para> in a dedicated build directory:</para>

View File

@ -54,14 +54,14 @@ mv -v gmp-&gmp-version; gmp
tar -xf ../mpc-&mpc-version;.tar.gz tar -xf ../mpc-&mpc-version;.tar.gz
mv -v mpc-&mpc-version; mpc</userinput></screen> mv -v mpc-&mpc-version; mpc</userinput></screen>
<para>If building on x86_64, change the default directory name for 64-bit <para>For x86_64 target, set the default directory name for
libraries to <quote>lib</quote>:</para> 64-bit libraries to <quote>lib</quote>. The command is unnecessary,
but harmless for 32-bit x86. If you are building for another target,
you may need to adjust the command for your target.</para>
<screen><userinput remap="pre">sed -e '/m64=/s/lib64/lib/' \
-i.orig gcc/config/i386/t-linux64</userinput></screen>
<screen><userinput remap="pre">case $(uname -m) in
x86_64)
sed -e '/m64=/s/lib64/lib/' -i.orig gcc/config/i386/t-linux64
;;
esac</userinput></screen>
<!-- <!--
<para>Fix an issue with GCC-10.1 when building with a cross <para>Fix an issue with GCC-10.1 when building with a cross
compiler:</para> compiler:</para>

View File

@ -49,15 +49,13 @@
-e 's/return kAltStackSize/return SIGSTKSZ * 4/' \ -e 's/return kAltStackSize/return SIGSTKSZ * 4/' \
-i libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp</userinput></screen> -i libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp</userinput></screen>
<para>If building on x86_64, change the default directory name for 64-bit <para>For x86_64 target, set the default directory name for
libraries to <quote>lib</quote>:</para> 64-bit libraries to <quote>lib</quote>. The command is unnecessary,
but harmless for 32-bit x86. If you are building for another target,
you may need to adjust the command for your target.</para>
<screen><userinput remap="pre">case $(uname -m) in <screen><userinput remap="pre">sed -e '/m64=/s/lib64/lib/' \
x86_64) -i.orig gcc/config/i386/t-linux64</userinput></screen>
sed -e '/m64=/s/lib64/lib/' \
-i.orig gcc/config/i386/t-linux64
;;
esac</userinput></screen>
<para>The GCC documentation recommends building GCC in a dedicated build directory:</para> <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>