Changes in / [fd531b84:1b61cd1]


Ignore:
Files:
25 edited

Legend:

Unmodified
Added
Removed

  • chapter02/creatingpartition.xml

    rfd531b84 r1b61cd1  
    105105
    106106    <sect3>
    107     <title>The Grub Bios Partition</title>
    108 
    109     <para>If the <emphasis>boot disk</emphasis> has been partitioned with a
    110     GUID Partition Table (GPT), then a small, typically 1 MB, partition must be
    111     created if it does not already exist.  This partition is not formatted, but
    112     must be available for GRUB to use during installation of the boot
    113     loader. This partition will normally be labeled 'BIOS Boot' if using
    114     <command>fdisk</command> or have a code of <emphasis>EF02</emphasis> if
    115     using the <command>gdisk</command> command.</para>
    116 
    117     <note><para>The Grub Bios partition must be on the drive that the BIOS
    118     uses to boot the system.  This is not necessarily the drive that holds
    119     the LFS root partition. The disks on a system may use different
    120     partition table types. The necessity of the Grub Bios partition depends
    121     only on the partition table type of the boot disk.</para></note>
    122     </sect3>
    123 
    124     <sect3>
    125107    <title>Convenience Partitions</title>
    126108

  • chapter04/addinguser.xml

    rfd531b84 r1b61cd1  
    8181  <systemitem class="username">lfs</systemitem> the owner:</para>
    8282
    83 <screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}
    84 case $(uname -m) in
    85   x86_64) chown -v lfs $LFS/lib64 ;;
    86 esac</userinput></screen>
     83<screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}</userinput></screen>
    8784
    8885<note><para>In some host systems, the following <command>su</command> command does not complete

  • chapter04/creatingminlayout.xml

    rfd531b84 r1b61cd1  
    2626for i in bin lib sbin; do
    2727  ln -sv usr/$i $LFS/$i
    28 done
    29 
    30 case $(uname -m) in
    31   x86_64) mkdir -pv $LFS/lib64 ;;
    32 esac</userinput></screen>
     28done</userinput></screen>
    3329
    3430  <para>Programs in <xref linkend="chapter-temporary-tools"/> will be compiled

  • chapter05/gcc-pass1.xml

    rfd531b84 r1b61cd1  
    6363mv -v mpc-&mpc-version; mpc</userinput></screen>
    6464
    65     <para>On x86_64 hosts, set the default directory name for
     65    <para>On ARM64 hosts, set the default directory name for
    6666    64-bit libraries to <quote>lib</quote>:</para>
    6767
    68 <screen><userinput remap="pre">case $(uname -m) in
    69   x86_64)
    70     sed -e '/m64=/s/lib64/lib/' \
    71         -i.orig gcc/config/i386/t-linux64
    72  ;;
    73 esac</userinput></screen>
     68<screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
     69    -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
    7470
    7571    <para>The GCC documentation recommends building GCC
    … …  
    160156        <term><parameter>--disable-multilib</parameter></term>
    161157        <listitem>
    162           <para>On x86_64, LFS does not support a multilib configuration.
    163           This switch is harmless for x86.</para>
     158          <para>On ARM64, LFS does not support a multilib configuration.</para>
    164159        </listitem>
    165160      </varlistentry>

  • chapter05/glibc.xml

    rfd531b84 r1b61cd1  
    4343  <sect2 role="installation">
    4444    <title>Installation of Glibc</title>
    45 
    46     <para>First, create a symbolic link for LSB compliance. Additionally,
    47     for x86_64, create a compatibility symbolic link required for proper
    48     operation of the dynamic library loader:</para>
    49 
    50 <screen><userinput remap="pre">case $(uname -m) in
    51     i?86)   ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
    52     ;;
    53     x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
    54             ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3
    55     ;;
    56 esac</userinput></screen>
    57 
    58     <note>
    59       <para>
    60         The above command is correct.  The <command>ln</command> command has
    61         several syntactic versions, so be sure to check
    62         <command>info coreutils ln</command> and <filename>ln(1)</filename>
    63         before reporting what may appear to be an error.
    64       </para>
    65     </note>
    6645
    6746    <para>Some of the Glibc programs use the non-FHS-compliant
    … …  
    202181      and the output of the last command will be of the form:</para>
    203182
    204 <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
    205 
    206       <para>Note that for 32-bit machines, the interpreter name will be
    207       <filename>/lib/ld-linux.so.2</filename>.</para>
     183<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen>
     184
     185      <para>Note that for big-endian machines, the interpreter name will be
     186          <filename>/lib/ld-linux-aarch64_be.so.1</filename>.</para>
    208187
    209188      <para>If the output is not as shown above, or there is no output at all,

  • chapter06/gcc-pass2.xml

    rfd531b84 r1b61cd1  
    5858mv -v mpc-&mpc-version; mpc</userinput></screen>
    5959
    60     <para>If building on x86_64, change the default directory name for 64-bit
    61     libraries to <quote>lib</quote>:</para>
     60    <para>On ARM64 hosts, set the default directory name for
     61    64-bit libraries to <quote>lib</quote>:</para>
    6262
    63 <screen><userinput remap="pre">case $(uname -m) in
    64   x86_64)
    65     sed -e '/m64=/s/lib64/lib/' -i.orig gcc/config/i386/t-linux64
    66   ;;
    67 esac</userinput></screen>
     63<screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
     64    -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
    6865
    6966    <para>Override the building rule of libgcc and libstdc++ headers, to

  • chapter07/changingowner.xml

    rfd531b84 r1b61cd1  
    3434  command:</para>
    3535
    36 <screen><userinput>chown -R root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}
    37 case $(uname -m) in
    38   x86_64) chown -R root:root $LFS/lib64 ;;
    39 esac</userinput></screen>
     36<screen><userinput>chown -R root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}</userinput></screen>
    4037
    4138</sect1>

  • chapter08/binutils.xml

    rfd531b84 r1b61cd1  
    116116          ultimately be located) is set to <filename
    117117          class="directory">$(exec_prefix)/$(target_alias)</filename>. For
    118           example, x86_64 machines would expand that to <filename
    119           class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is
     118          example, ARM64 machines would expand that to <filename
     119          class="directory">/usr/aarch64-unknown-linux-gnu</filename>. Because this is
    120120          a custom system, this target-specific directory in <filename
    121121          class="directory">/usr</filename> is not required. <filename
    … …  
    141141
    142142<screen><userinput remap="test">grep '^FAIL:' $(find -name '*.log')</userinput></screen>
    143 
    144     <para>Twelve tests fail in the gold test suite when the
    145     <option>--enable-default-pie</option> and
    146     <option>--enable-default-ssp</option> options are passed to GCC.</para>
    147143
    148144    <para>Install the package:</para>

  • chapter08/expect.xml

    rfd531b84 r1b61cd1  
    4848  <sect2 role="installation">
    4949    <title>Installation of Expect</title>
     50
     51    <para>Update two config scripts to allow building this package for
     52    AArch64:</para>
     53
     54<screen><userinput remap="pre">tar -C tclconfig -xf ../autoconf-&autoconf-version;.tar.xz --strip-components=2 \
     55    autoconf-&autoconf-version;/build-aux/config.{guess,sub}</userinput></screen>
    5056
    5157    <para>Prepare Expect for compilation:</para>

  • chapter08/findutils.xml

    rfd531b84 r1b61cd1  
    4848    <para>Prepare Findutils for compilation:</para>
    4949
    50 <screen><userinput remap="configure">case $(uname -m) in
    51     i?86)   TIME_T_32_BIT_OK=yes ./configure --prefix=/usr --localstatedir=/var/lib/locate ;;
    52     x86_64) ./configure --prefix=/usr --localstatedir=/var/lib/locate ;;
    53 esac</userinput></screen>
     50<screen><userinput remap="configure">./configure --prefix=/usr --localstatedir=/var/lib/locate</userinput></screen>
    5451
    5552    <variablelist>
    5653      <title>The meaning of the configure options:</title>
    57 
    58       <varlistentry>
    59         <term><command>TIME_32_BIT_OK=yes</command></term>
    60         <listitem>
    61           <para>This setting is needed for building on a 32 bit system.</para>
    62         </listitem>
    63       </varlistentry>
    6454
    6555      <varlistentry>

  • chapter08/gcc.xml

    rfd531b84 r1b61cd1  
    5555    <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen>
    5656-->
    57     <para>If building on x86_64, change the default directory name for 64-bit
    58     libraries to <quote>lib</quote>:</para>
    59 
    60 <screen><userinput remap="pre">case $(uname -m) in
    61   x86_64)
    62     sed -e '/m64=/s/lib64/lib/' \
    63         -i.orig gcc/config/i386/t-linux64
    64   ;;
    65 esac</userinput></screen>
     57    <para>On ARM64 hosts, set the default directory name for
     58    64-bit libraries to <quote>lib</quote>:</para>
     59
     60<screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
     61    -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
    6662
    6763    <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>
    … …  
    161157    <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
    162158
    163     <para>Eleven tests in the i386 test suite for the gcc compiler are known to FAIL.
    164     It's because the test files do not account for the
     159    <para>In gcc tests, the tests related to
     160    <filename>fuse_adrp_add_1.c</filename>,
     161    <filename>pr63304_1.c</filename>,
     162    <filename>pr70120-2.c</filename>,
     163    <filename>pr78733.c</filename>,
     164    <filename>pr78796.c</filename>,
     165    <filename>pr79041-2.c</filename>,
     166    <filename>pr94530.c</filename>,
     167    <filename>pr94577.c</filename>,
     168    <filename>reload-valid-spoff.c</filename>, and
     169    many <filename>aapcs64</filename> tests are known to fail.
     170    They are because the test files do not account for the
    165171    <parameter>--enable-default-pie</parameter> option.</para>
    166172
    167     <para>Four tests related to PR100400 may be reported
    168     as both XPASS and FAIL when testing the g++ compiler; the test file
     173    <para>In gcc tests, the tests related to
     174    <filename>pr104005.c</filename>,
     175    <filename>pr103147-10.C</filename>,
     176    <filename>shrink_wrap_1.c</filename>,
     177    <filename>stack-check-cfa-1.c</filename>,
     178    <filename>stack-check-cfa-2.c</filename>,
     179    <filename>test_frame_17.c</filename>, and
     180    many <filename>sve/pcs</filename> tests are known
     181    to fail.  The g++ test related to <filename>pr103147-10.C</filename>
     182    is known to fail.  They are because the test files do not account for
     183    the <parameter>--enable-default-ssp</parameter> option.</para>
     184
     185    <para>In g++, four tests related to PR100400 are known to be reported
     186    as both XPASS and FAIL.  It's because the test file for this known issue
    169187    is not well written.</para>
     188
     189    <!-- Already known via gcc-testresults@gcc.gnu.org -->
     190    <para>On ARM64,
     191    four g++ tests related to <filename>Waddress-5.C</filename>,
     192    twelve g++ tests related to <filename>attrs-10.C</filename>,
     193    four g++ tests related to <filename>declare-simd-8.C</filename>,
     194    one gcc tests related to <filename>ssa-dom-thread-7.c</filename>,
     195    one gcc tests related to <filename>fcsel_1.c</filename>,
     196    one gcc tests related to <filename>mgeneral-regs_3.c</filename>,
     197    one gcc tests related to <filename>auto-init-7.c</filename>, and
     198    four gcc tests related to <filename>vqdmlalh_laneq*.c</filename>
     199    are known to fail.</para>
     200
     201    <!-- Need further investigation -->
     202    <para>Many gcc and g++ tests related to hwasan are known to fail.</para>
    170203
    171204    <para>A few unexpected failures cannot always be avoided. The GCC developers
    … …  
    224257  platform-specific differences in the dynamic linker name):</para>
    225258
    226 <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
     259<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen>
    227260
    228261  <para>Now make sure that we're set up to use the correct start files:</para>
    … …  
    232265  <para>The output of the last command should be:</para>
    233266
    234 <screen><computeroutput>/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
    235 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
    236 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
     267<screen><computeroutput>/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
     268/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
     269/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
    237270
    238271  <para>Depending on your machine architecture, the above may differ slightly.
    … …  
    251284
    252285<screen><computeroutput>#include &lt;...&gt; search starts here:
    253  /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include
     286 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include
    254287 /usr/local/include
    255  /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed
     288 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include-fixed
    256289 /usr/include</computeroutput></screen>
    257290
    … …  
    266299  be ignored, but otherwise the output of the last command should be:</para>
    267300
    268 <screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
     301<screen><computeroutput>SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib64")
    269302SEARCH_DIR("/usr/local/lib64")
    270303SEARCH_DIR("/lib64")
    271304SEARCH_DIR("/usr/lib64")
    272 SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
     305SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib")
    273306SEARCH_DIR("/usr/local/lib")
    274307SEARCH_DIR("/lib")
    275308SEARCH_DIR("/usr/lib");</computeroutput></screen>
    276 
     309<!--
    277310   <para>A 32-bit system may use a few other directories. For example, here
    278311   is the output from an i686 machine:</para>
    … …  
    286319SEARCH_DIR("/lib")
    287320SEARCH_DIR("/usr/lib");</computeroutput></screen>
    288 
     321-->
    289322  <para>Next make sure that we're using the correct libc:</para>
    290323
    … …  
    302335  platform-specific differences in dynamic linker name):</para>
    303336
    304 <screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>
     337<screen><computeroutput>found ld-linux-aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen>
    305338
    306339  <para>If the output does not appear as shown above or is not received

  • chapter08/glibc.xml

    rfd531b84 r1b61cd1  
    446446
    447447    <para>By default, the dynamic loader (<filename
    448     class="libraryfile">/lib/ld-linux.so.2</filename>) searches through
     448    class="libraryfile">/lib/ld-linux-aarch64.so.1</filename>) searches through
    449449    <filename class="directory">/usr/lib</filename> for dynamic libraries
    450450    that are needed by programs as they are run. However, if there are
    … …  
    494494        <seg>gencat, getconf, getent, iconv, iconvconfig, ldconfig,
    495495        ldd, lddlibc4,
    496         ld.so (symlink to ld-linux-x86-64.so.2 or ld-linux.so.2),
     496        ld.so (symlink to ld-linux-aarch64[_be].so.1),
    497497        locale, localedef, makedb, mtrace, nscd,
    498498        pcprofiledump, pldd, sln, sotruss, sprof, tzselect, xtrace,
    499499        zdump, and zic</seg>
    500         <seg>ld-linux-x86-64.so.2, ld-linux.so.2,
     500        <seg>ld-linux-aarch64[_be].so.1,
    501501        libBrokenLocale.{a,so}, libanl.{a,so},
    502502        libc.{a,so}, libc_nonshared.a, libc_malloc_debug.so,

  • chapter08/gmp.xml

    rfd531b84 r1b61cd1  
    4141  <sect2 role="installation">
    4242    <title>Installation of GMP</title>
    43 
    44     <note>
    45       <para>If you are building for 32-bit x86, but you have a CPU which is
    46       capable of running 64-bit code <emphasis>and</emphasis> you have specified
    47       <envar>CFLAGS</envar> in the environment, the configure script will
    48       attempt to configure for 64-bits and fail.
    49       Avoid this by invoking the configure command below with
    50 <screen role="nodump"><userinput><parameter>ABI=32</parameter> ./configure ...</userinput></screen></para>
    51     </note>
    5243
    5344    <note>
    … …  
    10798    applications using the gmp libraries with the message "Illegal
    10899    instruction".  In this case, gmp should be reconfigured with the option
    109     --build=x86_64-pc-linux-gnu and rebuilt.</para></caution>
     100    --build=aarch64-unknown-linux-gnu and rebuilt.</para></caution>
    110101
    111102    <para>Ensure that all 197 tests in the test suite passed.

  • chapter08/grub.xml

    rfd531b84 r1b61cd1  
    4343    <note>
    4444      <para>
     45        On ARM64 systems, the following instruction builds GRUB for UEFI.
     46        But the built GRUB lacks some features because a few optional
     47        dependencies of GRUB for UEFI is beyond the scope of LFS and not
     48        installed yet.
     49      </para>
     50      <para>
     51        If your system firmware does not support UEFI, you need to skip the
     52        content of this page and try to figure out how to boot your system.
     53      </para>
     54      <para>
    4555        If your system has UEFI support and you wish to boot LFS with UEFI,
    4656        you can skip this package in LFS,
    4757        and install GRUB with UEFI support (and its dependencies) by following
    4858        the instructions on
    49         <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink>.
     59        <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink>
     60        (with <parameter>--target=x86_64</parameter> removed).
    5061      </para>
    5162    </note>
    … …  
    7081
    7182<screen><userinput remap='pre'>patch -Np1 -i ../grub-&grub-version;-upstream_fixes-1.patch</userinput></screen>
     83
     84    <!--https://git.savannah.gnu.org/cgit/grub.git/commit/?id=69edb312 -->
     85    <para>Apply an upstream change so GRUB will be capable to load
     86    compressed kernel image on an ARM64 system:</para>
     87
     88<screen><userinput remap='pre'>sed '/ARMXX_MAGIC/,+2d' -i grub-core/loader/arm64/linux.c</userinput></screen>
    7289
    7390    <para>Prepare GRUB for compilation:</para>

  • chapter08/kbd.xml

    rfd531b84 r1b61cd1  
    4545    across the keymaps in the Kbd package. The following patch fixes this
    4646    issue for i386 keymaps:</para>
     47
     48    <note>
     49      <para>
     50        Don't skip the patch just because it mentions "i386".  The keymaps
     51        for the keyboards most common on the market (qwerty or dvorak) are
     52        in "i386" catagory.
     53      </para>
     54    </note>
    4755
    4856<screen><userinput remap="pre">patch -Np1 -i ../&kbd-backspace-patch;</userinput></screen>

  • chapter08/libcap.xml

    rfd531b84 r1b61cd1  
    6060          <para>This parameter sets the library directory to
    6161          <filename>/usr/lib</filename> rather than
    62           <filename>/usr/lib64</filename> on x86_64. It has no effect on
    63           x86.</para>
     62          <filename>/usr/lib64</filename> on ARM64.</para>
    6463        </listitem>
    6564      </varlistentry>

  • chapter08/libffi.xml

    rfd531b84 r1b61cd1  
    7777          system, use the less capable system as a parameter. For details
    7878          about alternative system types, see <ulink
    79           url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/x86-Options.html'>
    80           the x86 options in the GCC manual</ulink>.</para>
     79          url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/AArch64-Options.html'>
     80          the AArch64 options in the GCC manual</ulink>.</para>
    8181        </listitem>
    8282      </varlistentry>

  • chapter08/stripping.xml

    rfd531b84 r1b61cd1  
    4747  rationale for using the <command>install</command> command here.)</para>
    4848
    49   <note><para>The ELF loader's name is ld-linux-x86-64.so.2 on 64-bit systems
    50   and ld-linux.so.2 on 32-bit systems.  The construct below selects the
     49  <note><para>The ELF loader's name is ld-linux-aarch64.so.1 on
     50  little-endian systems and ld-linux-aarch64_be.so.1 on big-endian systems.
     51  The construct below selects the
    5152  correct name for the current architecture, excluding anything ending
    5253  with <quote>g</quote>, in case the commands below have already been

  • chapter08/util-linux.xml

    rfd531b84 r1b61cd1  
    129129        eject, fallocate, fdisk, fincore, findfs, findmnt, flock, fsck,
    130130        fsck.cramfs, fsck.minix, fsfreeze, fstrim, getopt, hardlink, hexdump, hwclock,
    131         i386 (link to setarch), ionice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last,
     131        ionice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last,
    132132        lastb (link to last), ldattach, linux32 (link to setarch), linux64 (link to setarch),
    133133        logger, look, losetup, lsblk, lscpu, lsipc, lsirq, lsfd, lslocks, lslogins,
    … …  
    138138        swapoff, swapon, switch_root, taskset, uclampset, ul,
    139139        umount, uname26 (link to setarch), unshare, utmpdump, uuidd, uuidgen, uuidparse,
    140         wall, wdctl, whereis, wipefs, x86_64 (link to setarch), and zramctl</seg>
     140        wall, wdctl, whereis, wipefs, and zramctl</seg>
    141141        <seg>libblkid.so, libfdisk.so, libmount.so,
    142142        libsmartcols.so, and libuuid.so</seg>
    … …  
    521521      </varlistentry>
    522522
    523       <varlistentry id="i386">
    524         <term><command>i386</command></term>
    525         <listitem>
    526           <para>A symbolic link to setarch</para>
    527           <indexterm zone="ch-system-util-linux i386">
    528             <primary sortas="b-i386">i386</primary>
    529           </indexterm>
    530         </listitem>
    531       </varlistentry>
    532 
    533523      <varlistentry id="ionice">
    534524        <term><command>ionice</command></term>
    … …  
    12801270      </varlistentry>
    12811271
    1282       <varlistentry id="x86_64">
    1283         <term><command>x86_64</command></term>
    1284         <listitem>
    1285           <para>A symbolic link to setarch</para>
    1286           <indexterm zone="ch-system-util-linux x86_64">
    1287             <primary sortas="b-x86_64">x86_64</primary>
    1288           </indexterm>
    1289         </listitem>
    1290       </varlistentry>
    1291 
    12921272      <varlistentry id="zramctl">
    12931273        <term><command>zramctl</command></term>

  • chapter10/grub.xml

    rfd531b84 r1b61cd1  
    1919  <note>
    2020    <para>
    21       If your system has UEFI support and you wish to boot LFS with UEFI,
    22       you should skip this page, and configure GRUB with UEFI support
     21      This section assume your system has UEFI support and you wish to boot
     22      LFS with UEFI and GRUB built following the instructions in Chapter 8.
     23    </para>
     24    <para>
     25      If you've installed GRUB for UEFI with optional dependencies following
     26      BLFS, you should skip this page, and configure GRUB with UEFI support
    2327      using the instructions provided in
    24       <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>.
     28      <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>,
     29      but replace <parameter>--target=x86_64-efi</parameter> with
     30      <parameter>--target=arm64-efi</parameter> for the ARM64 system.
     31    </para>
     32    <para>
     33      If your system does not support UEFI or you don't want to use it,
     34      you'll need to figure out how to configure the booting process of
     35      the system on your own.
    2536    </para>
    2637  </note>
    … …  
    3546    LILO.</para></warning>
    3647
    37     <para> Ensure that an emergency boot disk is ready to <quote>rescue</quote>
     48    <para>Ensure that an emergency boot disk is ready to <quote>rescue</quote>
    3849    the computer if the computer becomes unusable (un-bootable).  If you do not
    39     already have a boot device, you can create one.  In order for the procedure
    40     below to work, you need to jump ahead to BLFS and install
    41     <userinput>xorriso</userinput> from the <ulink
    42     url="&blfs-book;multimedia/libisoburn.html">
    43     libisoburn</ulink> package.</para>
    44 
    45 <screen role="nodump"><userinput>cd /tmp
    46 grub-mkrescue --output=grub-img.iso
    47 xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></screen>
    48 
     50    already have a boot device, you can create one.  To create a emergency
     51    boot device for UEFI, consult section <quote>Create an Emergency Boot
     52    Disk</quote> in
     53        <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>.</para>
     54
     55  </sect2>
     56
     57  <sect2>
     58    <title>Turn off Secure Boot</title>
     59
     60    <para>LFS does not have the essential packages to support Secure Boot.
     61    To set up the boot process following the instructions in this section,
     62    Secure Boot must be turned off from the configuration interface of the
     63    firmware. Read the documentation provided by the manufacturer of your
     64    system to find out how.</para>
    4965  </sect2>
    5066
    … …  
    7288    <title>Setting Up the Configuration</title>
    7389
    74     <para>GRUB works by writing data to the first physical track of the
    75     hard disk.  This area is not part of any file system.  The programs
    76     there access GRUB modules in the boot partition.  The default location
    77     is /boot/grub/.</para>
     90    <para>GRUB works by creating an EFI executable in the EFI System
     91    Partition (ESP).  You can find the ESP with:</para>
     92
     93<screen role="nodump"><userinput>fdisk -l | grep 'EFI System'</userinput></screen>
     94
     95    <para>If no ESP exists on your hard drive (for example, you are building
     96    LFS on a fresh new system with a Live CD as the host distro), read
     97    <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>
     98    for the instruction to create an ESP on your hard drive.</para>
     99
     100    <para>If the ESP is not mounted at
     101    <filename class="directory">/boot/efi</filename> (in the chroot),
     102    mount it now:</para>
     103
     104<screen role="nodump"><userinput>mkdir -pv /boot/efi
     105mount /boot/efi</userinput></screen>
     106
     107    <note>
     108      <para>The path to the device node is intentionally omitted in the
     109      command.  We expect the entry for mounting the ESP to
     110      <filename class="directory">/boot/efi</filename> is already in
     111      <filename>/etc/fstab</filename>.  Add the entry before running the
     112      command if you forgot to create an entry for the ESP in
     113      <xref linkend="ch-bootable-fstab"/>.</para>
     114    </note>
    78115
    79116    <para>The location of the boot partition is a choice of the user that
    … …  
    100137
    101138    <para>Install the GRUB files into <filename
    102     class="directory">/boot/grub</filename> and set up the boot track:</para>
     139    class="directory">/boot/grub</filename> and the GRUB EFI executable into
     140    <filename class="directory">/boot/efi/EFI/BOOTAA64.EFI</filename>:</para>
    103141
    104142    <warning>
    105       <para>The following command will overwrite the current boot loader. Do not
    106       run the command if this is not desired, for example, if using a third party
    107       boot manager to manage the Master Boot Record (MBR).</para>
     143      <para>The following command will overwrite
     144      <filename>BOOTAA64.EFI</filename>. Do not run the command if this is
     145      not desired, for example, if it contains a third party boot manager.
     146      You can backup it with <command>cp</command> as it's a regular
     147      file.</para>
    108148    </warning>
    109149
    110 <screen role="nodump"><userinput>grub-install /dev/sda</userinput></screen>
     150<screen role="nodump"><userinput>grub-install --removable</userinput></screen>
    111151
    112152    <note>
    113       <para>If the system has been booted using UEFI,
    114       <command>grub-install</command> will try to install files for the
    115       <emphasis>x86_64-efi</emphasis> target, but those files
    116       have not been installed in <xref linkend="chapter-building-system"/>.
    117       If this is the case, add <option>--target i386-pc</option> to the
    118       command above.</para>
     153      <para>
     154        <parameter>--removable</parameter> may seem strange here.  The UEFI
     155        firmware searches EFI executables for boot loaders in a hardcoded
     156        path, <filename>EFI/BOOTAA64.EFI</filename> in the ESP, and other
     157        boot loader paths listed in the EFI variables.  We've not installed
     158        the utilities for manipulating EFI variables so we need to install
     159        the EFI executable into the hardcoded path.  The hardcoded path is
     160        usually used by removable devices (for example, USB thumb devices)
     161        so the <command>grub-install</command> option for this purpose is
     162        named <parameter>--removable</parameter>.
     163      </para>
     164      <para>
     165        UEFI implementation usually prefers the boot loaders with paths
     166        recorded in an EFI variable, to the boot loader with the hardcoded
     167        search path.  You may need to invoke the boot device selection menu
     168        or setting interface of your EFI firmware on next boot to explicitly
     169        select the bootloader.
     170      </para>
     171      <para>
     172        Some UEFI implementation may completely skip the hardcoded path if
     173        there are other boot loaders in the same hard drive with paths
     174        recorded in an EFI variable.  Then you need to create an EFI
     175        variable for the newly installed boot loader.  Install
     176        <ulink url="&blfs-book;postlfs/efibootmgr.html">efibootmgr</ulink>,
     177        then run the following commands:
     178
     179<screen role="nodump"><userinput>mount -v -t efivarfs efivarfs /sys/firmware/efi/efivars
     180efibootmgr -B -L LFS || true
     181efibootmgr -c -L LFS -l '\EFI\BOOT\BOOTAA64.EFI' -d /dev/sda
     182umount /sys/firmware/efi/efivars</userinput></screen>
     183
     184        Replace <filename>/dev/sda</filename> with the device node of the
     185        hard drive where you are installing GRUB into.  For some UEFI
     186        firmwares, <option>-e 3</option> option may be needed for the
     187        <command>efibootmgr -c</command> command.
     188      </para>
    119189    </note>
    120190

  • chapter10/kernel.xml

    rfd531b84 r1b61cd1  
    142142   [*]   Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
    143143Device Drivers  ---&gt;
     144  Firmware Drivers   ---&gt;
     145   EFI (Extensible Firmware Interface) Support  ---&gt;
     146     [*] Enable the generic EFI decompressor [CONFIG_EFI_ZBOOT]
    144147  Graphics support ---&gt;
    145148   Frame buffer Devices ---&gt;
    … …  
    182185  Firmware Drivers   ---&gt;
    183186   [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
     187   EFI (Extensible Firmware Interface) Support  ---&gt;
     188     [*] Enable the generic EFI decompressor [CONFIG_EFI_ZBOOT]
    184189  Graphics support ---&gt;
    185190   Frame buffer Devices ---&gt;
    … …  
    192197        [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen>
    193198
    194       <para>Enable some additional features if you are building a 64-bit
    195       system.  If you are using menuconfig, enable them in the order of
    196       <parameter>CONFIG_PCI_MSI</parameter> first, then
    197       <parameter>CONFIG_IRQ_REMAP</parameter>, at last
    198       <parameter>CONFIG_X86_X2APIC</parameter> because an option only
    199       shows up after its dependencies are selected.</para>
    200 
    201       <screen role="nodump">Processor type and features ---&gt;
    202   [*] Support x2apic [CONFIG_X86_X2APIC]
    203 Device Drivers ---&gt;
    204   [*] PCI Support ---&gt; [CONFIG_PCI]
    205     [*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI]
    206   [*] IOMMU Hardware Support ---&gt; [CONFIG_IOMMU_SUPPORT]
    207     [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen>
    208 
    209       <para>If you are building a 32-bit system running on a hardware
    210       with RAM more than 4GB, adjust the configuration so the kernel will
    211       be able to use up to 64GB physical RAM:</para>
    212 
    213       <screen role="nodump">Processor type and features ---&gt;
    214   High Memory Support ---&gt;
    215     (X) 64GB [CONFIG_HIGHMEM64G]</screen>
    216 
    217199      <para>If the partition for the LFS system is in a NVME SSD (i. e. the
    218200      device node for the partition is <filename>/dev/nvme*</filename>
    … …  
    327309          upon switching to root filesystem just before starting
    328310          init.</para>
     311        </listitem>
     312      </varlistentry>
     313
     314      <varlistentry>
     315        <term><parameter>Enable the generic EFI decompressor</parameter></term>
     316        <listitem>
     317          <para>Create the bootable image as an EFI application that carries
     318          the actual kernel image in compressed form.  It can make the
     319          bootable image 50% smaller.</para>
    329320        </listitem>
    330321      </varlistentry>
    … …  
    344335      </varlistentry>
    345336
    346       <varlistentry>
    347         <term><parameter>Support x2apic</parameter></term>
    348         <listitem>
    349           <para>Support running the interrupt controller of 64-bit x86
    350           processors in x2APIC mode.  x2APIC may be enabled by firmware on
    351           64-bit x86 systems, and a kernel without this option enabled will
    352           panic on boot if x2APIC is enabled by firmware.  This option has
    353           has no effect, but also does no harm if x2APIC is disabled by the
    354           firmware.</para>
    355         </listitem>
    356       </varlistentry>
    357 
    358337    </variablelist>
    359338
    … …  
    410389    the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
    411390    the automatic setup of the boot process described in the next section.  The
    412     following command assumes an x86 architecture:</para>
    413 
    414 <screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
     391    following command assumes an ARM64 architecture with an EFI boot loader
     392    (for example, GRUB built in &ch-final;):</para>
     393
     394<screen><userinput remap="install">cp -iv arch/arm64/boot/vmlinuz.efi /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
    415395
    416396    <para><filename>System.map</filename> is a symbol file for the kernel.

  • general.ent

    rfd531b84 r1b61cd1  
    9292<!ENTITY test-results    "&lfs-root;lfs/build-logs/&generic-version;/">
    9393<!ENTITY secadv          "&lfs-root;lfs/advisories/">
    94 <!ENTITY min-kernel      "3.2">
     94<!ENTITY min-kernel      "3.7">
    9595<!--
    9696<!ENTITY patches-rootd   "&lfs-root;patches/lfs/&generic-versiond;/">

  • git-version.sh

    rfd531b84 r1b61cd1  
    4949
    5050sha="$(git describe --abbrev=1)"
    51 rev=$(echo "$sha" | sed 's/-g[^-]*$//')
     51rev=arm64-$(echo "$sha" | sed 's/-g[^-]*$//')
    5252version="$rev"
    5353versiond="$rev-systemd"

  • prologue/architecture.xml

    rfd531b84 r1b61cd1  
    1111  <title>LFS Target Architectures</title>
    1212
    13 <para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
    14 and x86_64 (64-bit) CPUs.  On the other hand, the instructions in this book are
    15 also known to work, with some modifications, with the Power PC and ARM CPUs. To
    16 build a system that utilizes one of these alternative CPUs, the main prerequisite, in
    17 addition to those on the next page, is an existing Linux system such as an
    18 earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution
    19 that targets that architecture. (Note that a 32-bit
    20 distribution can be installed and used as a host system on a 64-bit AMD/Intel
    21 computer.)</para>
     13<para>The target architectures of this LFS edition are ARM64 (sometimes
     14called AArch64) CPUs.  On the other hand, the instructions in this book may
     15work on 32-bit ARM CPUs with some modifications. To build a system that
     16utilizes one of these alternative CPUs, the main prerequisite, in
     17addition to those on
     18the next page, is an existing Linux system such as an earlier LFS
     19installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that
     20targets the architecture that you have.</para>
    2221
    23 <para>The gain from building on a 64-bit system, as
    24 compared to a 32-bit system, is minimal.
    25 For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system,
    26 using 4 cores, the following statistics were measured:</para>
    27 
    28 <screen><computeroutput>Architecture Build Time     Build Size
    29 32-bit       239.9 minutes  3.6 GB
    30 64-bit       233.2 minutes  4.4 GB</computeroutput></screen>
    31 
    32 <para>As you can see, on the same hardware, the 64-bit build is only 3% faster
    33 (and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP
    34 server, or a firewall, a 32-bit CPU may be good enough. On the other
    35 hand, several packages in BLFS now need more than 4 GB of RAM to be built
    36 and/or to run; if you plan to use LFS as a desktop, the LFS authors
    37 recommend building a 64-bit system.</para>
    38 
    39 <para>The default 64-bit build that results from LFS is a
    40 <quote>pure</quote> 64-bit system. That is, it supports 64-bit executables
    41 only. Building a <quote>multi-lib</quote> system requires compiling many
     22<para>The build results from this LFS edition is considered a
     23<quote>pure</quote> 64-bit system.  That is, it supports 64-bit executables
     24only.  Building a <quote>multi-lib</quote> system requires compiling many
    4225applications twice, once for a 32-bit system and once for a 64-bit system.
    4326This is not directly supported in LFS because it would interfere with the
    4427educational objective of providing the minimal instructions needed for a
    45 basic Linux system. Some of the LFS/BLFS editors maintain a multilib fork
     28base Linux system. Some LFS/BLFS editors maintain a multilib fork
    4629of LFS, accessible at <ulink
    4730url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But
    48 that's an advanced topic.</para>
     31the multilib edition is for x86_64, and multilib is an advanced topic
     32anyway.</para>
    4933
    5034</sect1>

  • prologue/standards.xml

    rfd531b84 r1b61cd1  
    3636        specifications are architecture specific.  There are also two trial
    3737        specifications: Gtk3 and Graphics.  LFS attempts to conform to the LSB
    38         specifications for the IA32 (32-bit x86) or AMD64 (x86_64)
    39         architectures discussed in the previous section.</para>
     38        generic specifications.  The architecture specific part of LSB does
     39        not exist for ARM64.</para>
    4040
    4141        <note><para>Many people do not agree with these requirements.
Note: See TracChangeset for help on using the changeset viewer.