arm64: various text change for references to architecture

This commit is contained in:
Xi Ruoyao 2022-08-26 19:43:31 +08:00
parent a56ef9163d
commit c8bc7430f3
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
5 changed files with 7 additions and 9 deletions

View File

@ -140,8 +140,7 @@ cd build</userinput></screen>
<varlistentry> <varlistentry>
<term><parameter>--disable-multilib</parameter></term> <term><parameter>--disable-multilib</parameter></term>
<listitem> <listitem>
<para>On x86_64, LFS does not support a multilib configuration. <para>On ARM64, LFS does not support a multilib configuration.</para>
This switch is harmless for x86.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>

View File

@ -138,8 +138,8 @@ cd build</userinput></screen>
<para>Normally, the tooldir (the directory where the executables will <para>Normally, the tooldir (the directory where the executables will
ultimately be located) is set to <filename ultimately be located) is set to <filename
class="directory">$(exec_prefix)/$(target_alias)</filename>. For class="directory">$(exec_prefix)/$(target_alias)</filename>. For
example, x86_64 machines would expand that to <filename example, ARM64 machines would expand that to <filename
class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is class="directory">/usr/aarch64-pc-linux-gnu</filename>. Because this is
a custom system, this target-specific directory in <filename a custom system, this target-specific directory in <filename
class="directory">/usr</filename> is not required. <filename class="directory">/usr</filename> is not required. <filename
class="directory">$(exec_prefix)/$(target_alias)</filename> would be class="directory">$(exec_prefix)/$(target_alias)</filename> would be

View File

@ -59,8 +59,7 @@
<listitem> <listitem>
<para>This parameter sets the library directory to <para>This parameter sets the library directory to
<filename>/usr/lib</filename> rather than <filename>/usr/lib</filename> rather than
<filename>/usr/lib64</filename> on x86_64. It has no effect on <filename>/usr/lib64</filename> on ARM64.</para>
x86.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>

View File

@ -71,8 +71,8 @@
will be copied from the native system to a less capable will be copied from the native system to a less capable
system, use the less capable system as a parameter. For details system, use the less capable system as a parameter. For details
about alternative system types, see <ulink about alternative system types, see <ulink
url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/x86-Options.html'> url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/AArch64-Options.html'>
the x86 options in the GCC manual</ulink>.</para> the AArch64 options in the GCC manual</ulink>.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>

View File

@ -289,7 +289,7 @@ File systems ---&gt;
used. The filename below can be changed to suit your taste, but the stem of used. The filename below can be changed to suit your taste, but the stem of
the filename should be <emphasis>vmlinuz</emphasis> to be compatible with the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
the automatic setup of the boot process described in the next section. The the automatic setup of the boot process described in the next section. The
following command assumes an x86 architecture:</para> following command assumes an ARM64 architecture:</para>
<screen><userinput remap="install">cp -iv arch/arm64/boot/Image /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> <screen><userinput remap="install">cp -iv arch/arm64/boot/Image /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>