More info about "deploying LFS"

This commit is contained in:
Xi Ruoyao 2025-03-09 13:08:32 +08:00
parent ed2611fa6f
commit a2bf74a9b5
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
2 changed files with 12 additions and 7 deletions

View File

@ -51,11 +51,14 @@
<para>Like GMP, Libffi builds with optimizations specific <para>Like GMP, Libffi builds with optimizations specific
to the processor in use. If building for another system, change the to the processor in use. If building for another system, change the
value of the <parameter>--with-gcc-arch=</parameter> parameter in the value of the <parameter>--with-gcc-arch=</parameter> parameter in the
following command to an architecture name fully implemented by the following command to an architecture name fully implemented by
<emphasis role='bold'>both</emphasis> the host CPU and the
CPU on that system. CPU on that system.
If this is not done, all applications that link to If this is not done, all applications that link to
<filename class='libraryfile'>libffi</filename> will trigger <filename class='libraryfile'>libffi</filename> will trigger
Illegal Operation Errors.</para> Illegal Operation Errors. If you cannot figure out a value
safe for both the CPUs, replace the parameter with
<option>--without-gcc-arch</option> to produce a generic library.</para>
</note> </note>
<para>Prepare Libffi for compilation:</para> <para>Prepare Libffi for compilation:</para>

View File

@ -370,11 +370,13 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
differences in system hardware and the original kernel differences in system hardware and the original kernel
configuration.</para> configuration.</para>
<note><para>There have been some reports of issues when copying between <important><para>If you want to deploy the LFS system onto a system
similar but not identical architectures. For instance, the instruction set with a different CPU, when you build <xref linkend='ch-system-gmp'/> and
for an Intel system is not identical with the AMD processor's instructions, and later <xref linkend='ch-system-libffi'/> you must follow the notes about
versions of some processors may provide instructions that are unavailable with overriding the architecture-specific optimization to produce libraries
earlier versions.</para></note> suitable for both the host system and the system(s) where you'll deploy
the LFS system. Otherwise you'll get <computeroutput>Illegal
Instruction</computeroutput> errors running LFS.</para></important>
<para>Finally, the new system has to be made bootable via <xref <para>Finally, the new system has to be made bootable via <xref
linkend="ch-bootable-grub"/>.</para> linkend="ch-bootable-grub"/>.</para>