Changes in / [04ca2a7:ceb61b9]
- Files:
-
- 25 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/creatingpartition.xml
r04ca2a7 rceb61b9 103 103 occurrence, the best solution is to purchase more RAM for your 104 104 system.</para> </sect3> 105 106 <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> 105 123 106 124 <sect3> -
chapter04/addinguser.xml
r04ca2a7 rceb61b9 81 81 <systemitem class="username">lfs</systemitem> the owner:</para> 82 82 83 <screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}</userinput></screen> 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> 84 87 85 88 <note><para>In some host systems, the following <command>su</command> command does not complete -
chapter04/creatingminlayout.xml
r04ca2a7 rceb61b9 26 26 for i in bin lib sbin; do 27 27 ln -sv usr/$i $LFS/$i 28 done</userinput></screen> 28 done 29 30 case $(uname -m) in 31 x86_64) mkdir -pv $LFS/lib64 ;; 32 esac</userinput></screen> 29 33 30 34 <para>Programs in <xref linkend="chapter-temporary-tools"/> will be compiled -
chapter05/gcc-pass1.xml
r04ca2a7 rceb61b9 63 63 mv -v mpc-&mpc-version; mpc</userinput></screen> 64 64 65 <para>On ARM64 hosts, set the default directory name for65 <para>On x86_64 hosts, set the default directory name for 66 66 64-bit libraries to <quote>lib</quote>:</para> 67 67 68 <screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \ 69 -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen> 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> 70 74 71 75 <para>The GCC documentation recommends building GCC … … 157 161 <term><parameter>--disable-multilib</parameter></term> 158 162 <listitem> 159 <para>On ARM64, LFS does not support a multilib configuration.</para> 163 <para>On x86_64, LFS does not support a multilib configuration. 164 This switch is harmless for x86.</para> 160 165 </listitem> 161 166 </varlistentry> -
chapter05/glibc.xml
r04ca2a7 rceb61b9 43 43 <sect2 role="installation"> 44 44 <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 a few syntactic versions, so be sure to check 62 <command>info coreutils ln</command> and <filename>ln(1)</filename> 63 before reporting what you may think is an error. 64 </para> 65 </note> 45 66 46 67 <para>Some of the Glibc programs use the non-FHS compliant … … 181 202 and the output of the last command will be of the form:</para> 182 203 183 <screen><computeroutput>[Requesting program interpreter: /lib /ld-linux-aarch64.so.1]</computeroutput></screen>184 185 <para>Note that for big-endianmachines, the interpreter name will be186 <filename>/lib/ld-linux-aarch64_be.so.1</filename>.</para>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> 187 208 188 209 <para>If the output is not shown as above or there was no output at all, -
chapter06/gcc-pass2.xml
r04ca2a7 rceb61b9 59 59 mv -v mpc-&mpc-version; mpc</userinput></screen> 60 60 61 <para> On ARM64 hosts, set the default directory name for62 64-bitlibraries to <quote>lib</quote>:</para>61 <para>If building on x86_64, change the default directory name for 64-bit 62 libraries to <quote>lib</quote>:</para> 63 63 64 <screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \ 65 -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen> 64 <screen><userinput remap="pre">case $(uname -m) in 65 x86_64) 66 sed -e '/m64=/s/lib64/lib/' -i.orig gcc/config/i386/t-linux64 67 ;; 68 esac</userinput></screen> 66 69 67 70 <para>Override the building rule of libgcc and libstdc++ headers, to -
chapter07/changingowner.xml
r04ca2a7 rceb61b9 34 34 command:</para> 35 35 36 <screen><userinput>chown -R root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}</userinput></screen> 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> 37 40 38 41 </sect1> -
chapter08/binutils.xml
r04ca2a7 rceb61b9 139 139 ultimately be located) is set to <filename 140 140 class="directory">$(exec_prefix)/$(target_alias)</filename>. For 141 example, ARM64 machines would expand that to <filename142 class="directory">/usr/ aarch64-unknown-linux-gnu</filename>. Because this is141 example, x86_64 machines would expand that to <filename 142 class="directory">/usr/x86_64-pc-linux-gnu</filename>. Because this is 143 143 a custom system, this target-specific directory in <filename 144 144 class="directory">/usr</filename> is not required. <filename … … 165 165 <screen><userinput remap="test">grep '^FAIL:' $(find -name '*.log')</userinput></screen> 166 166 167 <para> 167 <para>Twelve tests fail in the gold testsuite when the 168 <option>--enable-default-pie</option> and 169 <option>--enable-default-ssp</option> options are passed to GCC. 168 170 <!-- Caused by egrep deprecation. Note that we don't "patch" temp grep. 169 171 And it seems unworthy to add a sed into temp grep just for one test … … 171 173 anyway.) 172 174 Will be fixed in 2.40 (upstream commit 67d1991). --> 173 The test named <filename>ar with versioned solib</filename> is 175 The test named <filename>ar with versioned solib</filename> is also 174 176 known to fail. 175 177 <!-- https://sourceware.org/bugzilla/show_bug.cgi?id=29107 --> -
chapter08/expect.xml
r04ca2a7 rceb61b9 48 48 <sect2 role="installation"> 49 49 <title>Installation of Expect</title> 50 51 <para>Update two config scripts to allow building this package for52 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>56 50 57 51 <para>Prepare Expect for compilation:</para> -
chapter08/findutils.xml
r04ca2a7 rceb61b9 46 46 <para>Prepare Findutils for compilation:</para> 47 47 48 <screen><userinput remap="configure">./configure --prefix=/usr --localstatedir=/var/lib/locate</userinput></screen> 48 <screen><userinput remap="configure">case $(uname -m) in 49 i?86) TIME_T_32_BIT_OK=yes ./configure --prefix=/usr --localstatedir=/var/lib/locate ;; 50 x86_64) ./configure --prefix=/usr --localstatedir=/var/lib/locate ;; 51 esac</userinput></screen> 49 52 50 53 <variablelist> 51 54 <title>The meaning of the configure options:</title> 55 56 <varlistentry> 57 <term><command>TIME_32_BIT_OK=yes</command></term> 58 <listitem> 59 <para>This setting is needed for building on a 32 bit system.</para> 60 </listitem> 61 </varlistentry> 52 62 53 63 <varlistentry> -
chapter08/gcc.xml
r04ca2a7 rceb61b9 55 55 <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen> 56 56 --> 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> 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> 62 66 63 67 <para>The GCC documentation recommends building GCC in a dedicated build directory:</para> … … 157 161 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 158 162 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 163 <para>In gcc, eleven tests, in the i386 test suite are known to FAIL. 164 It's because the test files do not account for the 171 165 <parameter>--enable-default-pie</parameter> option.</para> 172 173 <para>In gcc tests, the tests related to174 <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>, and180 many <filename>sve/pcs</filename> tests are known181 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 for183 the <parameter>--enable-default-ssp</parameter> option.</para>184 166 185 167 <para>In g++, four tests related to PR100400 are known to be reported 186 168 as both XPASS and FAIL. It's because the test file for this known issue 187 169 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>, and197 four gcc tests related to <filename>vqdmlalh_laneq*.c</filename>198 are known to fail.</para>199 200 <!-- Need further investigation -->201 <para>Many gcc and g++ tests related to hwasan are known to fail.202 And, two tests related to <filename>thread_leak1.c</filename> are known203 to fail for both gcc and g++.</para>204 170 205 171 <para>A few unexpected failures cannot always be avoided. The GCC developers … … 258 224 platform-specific differences in the dynamic linker name):</para> 259 225 260 <screen><computeroutput>[Requesting program interpreter: /lib /ld-linux-aarch64.so.1]</computeroutput></screen>226 <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen> 261 227 262 228 <para>Now make sure that we're setup to use the correct start files:</para> … … 266 232 <para>The output of the last command should be:</para> 267 233 268 <screen><computeroutput>/usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded269 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded270 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>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> 271 237 272 238 <para>Depending on your machine architecture, the above may differ slightly. … … 285 251 286 252 <screen><computeroutput>#include <...> search starts here: 287 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/include253 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include 288 254 /usr/local/include 289 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/include-fixed255 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed 290 256 /usr/include</computeroutput></screen> 291 257 … … 300 266 be ignored, but otherwise the output of the last command should be:</para> 301 267 302 <screen><computeroutput>SEARCH_DIR("/usr/ aarch64-unknown-linux-gnu/lib64")268 <screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64") 303 269 SEARCH_DIR("/usr/local/lib64") 304 270 SEARCH_DIR("/lib64") 305 271 SEARCH_DIR("/usr/lib64") 306 SEARCH_DIR("/usr/ aarch64-unknown-linux-gnu/lib")272 SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib") 307 273 SEARCH_DIR("/usr/local/lib") 308 274 SEARCH_DIR("/lib") … … 336 302 platform-specific differences in dynamic linker name):</para> 337 303 338 <screen><computeroutput>found ld-linux- aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen>304 <screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen> 339 305 340 306 <para>If the output does not appear as shown above or is not received -
chapter08/glibc.xml
r04ca2a7 rceb61b9 448 448 449 449 <para>By default, the dynamic loader (<filename 450 class="libraryfile">/lib/ld-linux -aarch64.so.1</filename>) searches through450 class="libraryfile">/lib/ld-linux.so.2</filename>) searches through 451 451 <filename class="directory">/usr/lib</filename> for dynamic libraries 452 452 that are needed by programs as they are run. However, if there are … … 496 496 <seg>gencat, getconf, getent, iconv, iconvconfig, ldconfig, 497 497 ldd, lddlibc4, 498 ld.so (symlink to ld-linux- aarch64[_be].so.1),498 ld.so (symlink to ld-linux-x86-64.so.2 or ld-linux.so.2), 499 499 locale, localedef, makedb, mtrace, nscd, 500 500 pcprofiledump, pldd, sln, sotruss, sprof, tzselect, xtrace, 501 501 zdump, and zic</seg> 502 <seg>ld-linux- aarch64[_be].so.1,502 <seg>ld-linux-x86-64.so.2, ld-linux.so.2, 503 503 libBrokenLocale.{a,so}, libanl.{a,so}, 504 504 libc.{a,so}, libc_nonshared.a, libc_malloc_debug.so, -
chapter08/gmp.xml
r04ca2a7 rceb61b9 41 41 <sect2 role="installation"> 42 42 <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> 43 52 44 53 <note> … … 98 107 applications using the gmp libraries with the message "Illegal 99 108 instruction". In this case, gmp should be reconfigured with the option 100 --build= aarch64-unknown-linux-gnu and rebuilt.</para></caution>109 --build=x86_64-pc-linux-gnu and rebuilt.</para></caution> 101 110 102 111 <para>Ensure that all 197 tests in the test suite passed. -
chapter08/grub.xml
r04ca2a7 rceb61b9 43 43 <note> 44 44 <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> 55 If your system firmware supports UEFI and you want a fully 56 functional GRUB, you can skip the content of this page, 45 If your system has UEFI support and you wish to boot LFS with UEFI, 46 you can skip this package in LFS, 57 47 and install GRUB with UEFI support (and its dependencies) following 58 48 <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink> 59 (with <parameter>--target=x86_64</parameter> removed) at the end of 60 this chapter. 49 at the end of this chapter. 61 50 </para> 62 51 </note> -
chapter08/kbd.xml
r04ca2a7 rceb61b9 45 45 across the keymaps in the Kbd package. The following patch fixes this 46 46 issue for i386 keymaps:</para> 47 48 <note>49 <para>50 Don't skip the patch just because it mentions "i386". The keymaps51 for the keyboards most common on the market (qwerty or dvorak) are52 in "i386" catagory.53 </para>54 </note>55 47 56 48 <screen><userinput remap="pre">patch -Np1 -i ../&kbd-backspace-patch;</userinput></screen> -
chapter08/libcap.xml
r04ca2a7 rceb61b9 60 60 <para>This parameter sets the library directory to 61 61 <filename>/usr/lib</filename> rather than 62 <filename>/usr/lib64</filename> on ARM64.</para> 62 <filename>/usr/lib64</filename> on x86_64. It has no effect on 63 x86.</para> 63 64 </listitem> 64 65 </varlistentry> -
chapter08/libelf.xml
r04ca2a7 rceb61b9 60 60 61 61 <para>One test named <filename>run-low_high_pc.sh</filename> is known to 62 fail on ARM64.</para>62 fail on 32-bit x86 system.</para> 63 63 64 64 <para>Install only Libelf:</para> -
chapter08/libffi.xml
r04ca2a7 rceb61b9 72 72 system, use the less capable system as a parameter. For details 73 73 about alternative system types, see <ulink 74 url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/ AArch64-Options.html'>75 the AArch64options in the GCC manual</ulink>.</para>74 url='https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/x86-Options.html'> 75 the x86 options in the GCC manual</ulink>.</para> 76 76 </listitem> 77 77 </varlistentry> … … 96 96 97 97 <screen><userinput remap="test">make check</userinput></screen> 98 99 <!-- https://github.com/libffi/libffi/actions/runs/3084390461/jobs/4986488117 -->100 <para>90 tests are known to fail on ARM64.</para>101 98 102 99 <para>Install the package:</para> -
chapter08/stripping.xml
r04ca2a7 rceb61b9 47 47 rationale to use the <command>install</command> command here.</para> 48 48 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 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 52 51 correct name for the current architecture, excluding anything ending 53 52 with <quote>g</quote>, in case the commands below have already been -
chapter08/util-linux.xml
r04ca2a7 rceb61b9 127 127 eject, fallocate, fdisk, fincore, findfs, findmnt, flock, fsck, 128 128 fsck.cramfs, fsck.minix, fsfreeze, fstrim, getopt, hexdump, hwclock, 129 i onice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last, lastb (link to129 i386, ionice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last, lastb (link to 130 130 last), ldattach, linux32, linux64, logger, look, losetup, lsblk, lscpu, 131 131 lsipc, lsirq, lslocks, lslogins, lsmem, lsns, mcookie, mesg, mkfs, mkfs.bfs, mkfs.cramfs, mkfs.minix, mkswap, … … 135 135 swapoff (link to swapon), swapon, switch_root, taskset, uclampset, ul, 136 136 umount, uname26, unshare, utmpdump, uuidd, uuidgen, uuidparse, wall, wdctl, whereis, 137 wipefs, and zramctl</seg>137 wipefs, x86_64, and zramctl</seg> 138 138 <seg>libblkid.so, libfdisk.so, libmount.so, 139 139 libsmartcols.so, and libuuid.so</seg> … … 507 507 </varlistentry> 508 508 509 <varlistentry id="i386"> 510 <term><command>i386</command></term> 511 <listitem> 512 <para>A symbolic link to setarch</para> 513 <indexterm zone="ch-system-util-linux i386"> 514 <primary sortas="b-i386">i386</primary> 515 </indexterm> 516 </listitem> 517 </varlistentry> 518 509 519 <varlistentry id="ionice"> 510 520 <term><command>ionice</command></term> … … 1245 1255 </varlistentry> 1246 1256 1257 <varlistentry id="x86_64"> 1258 <term><command>x86_64</command></term> 1259 <listitem> 1260 <para>A symbolic link to setarch</para> 1261 <indexterm zone="ch-system-util-linux x86_64"> 1262 <primary sortas="b-x86_64">x86_64</primary> 1263 </indexterm> 1264 </listitem> 1265 </varlistentry> 1266 1247 1267 <varlistentry id="zramctl"> 1248 1268 <term><command>zramctl</command></term> -
chapter10/grub.xml
r04ca2a7 rceb61b9 19 19 <note> 20 20 <para> 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 config GRUB with UEFI support 21 If your system has UEFI support and you wish to boot LFS with UEFI, 22 you should skip this page, and config GRUB with UEFI support 27 23 using the instructions provided in 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. 24 <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>. 36 25 </para> 37 26 </note> … … 46 35 LILO.</para></warning> 47 36 48 <para> Ensure that an emergency boot disk is ready to <quote>rescue</quote>37 <para> Ensure that an emergency boot disk is ready to <quote>rescue</quote> 49 38 the computer if the computer becomes unusable (un-bootable). If you do not 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> 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 65 49 </sect2> 66 50 … … 88 72 <title>Setting Up the Configuration</title> 89 73 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 105 mount /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> 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> 115 78 116 79 <para>The location of the boot partition is a choice of the user that … … 136 99 137 100 <para>Install the GRUB files into <filename 138 class="directory">/boot/grub</filename> and the GRUB EFI executable into 139 <filename class="directory">/boot/efi/EFI/BOOTAA64.EFI</filename>:</para> 101 class="directory">/boot/grub</filename> and set up the boot track:</para> 140 102 141 103 <warning> 142 <para>The following command will overwrite 143 <filename>BOOTAA64.EFI</filename>. Do not run the command if this is 144 not desired, for example, if it contains a third party boot manager. 145 You can backup it with <command>cp</command> as it's a regular 146 file.</para> 104 <para>The following command will overwrite the current boot loader. Do not 105 run the command if this is not desired, for example, if using a third party 106 boot manager to manage the Master Boot Record (MBR).</para> 147 107 </warning> 148 108 149 <screen role="nodump"><userinput>grub-install --removable</userinput></screen>109 <screen role="nodump"><userinput>grub-install /dev/sda</userinput></screen> 150 110 151 111 <note> 152 <para> 153 <parameter>--removable</parameter> may seem strange here. The UEFI 154 firmware searches EFI executables for boot loaders in a hardcoded 155 path, <filename>EFI/BOOTAA64.EFI</filename> in the ESP, and other 156 boot loader paths listed in the EFI variables. We've not installed 157 the utilities for manipulating EFI variables so we need to install 158 the EFI executable into the hardcoded path. The hardcoded path is 159 usually used by removable devices (for example, USB thumb devices) 160 so the <command>grub-install</command> option for this purpose is 161 named <parameter>--removable</parameter>. 162 </para> 163 <para> 164 UEFI implementation usually prefers the boot loaders with paths 165 recorded in an EFI variable, to the boot loader with the hardcoded 166 search path. You may need to invoke the boot device selection menu 167 or setting interface of your EFI firmware on next boot to explicitly 168 select the bootloader. 169 </para> 170 <para> 171 Some UEFI implementation may completely skip the hardcoded path if 172 there are other boot loaders in the same hard drive with paths 173 recorded in an EFI variable. Then you need to create an EFI 174 variable for the newly installed boot loader. Install 175 <ulink url="&blfs-book;postlfs/efibootmgr.html">efibootmgr</ulink>, 176 then run the following commands: 177 178 <screen role="nodump"><userinput>mount -v -t efivarfs efivarfs /sys/firmware/efi/efivars 179 efibootmgr -B -L LFS || true 180 efibootmgr -c -L LFS -l '\EFI\BOOT\BOOTAA64.EFI' -d /dev/sda 181 umount /sys/firmware/efi/efivars</userinput></screen> 182 183 Replace <filename>/dev/sda</filename> with the device node of the 184 hard drive where you are installing GRUB into. For some UEFI 185 firmwares, <option>-e 3</option> option may be needed for the 186 <command>efibootmgr -c</command> command. 187 </para> 112 <para>If the system has been booted using UEFI, 113 <command>grub-install</command> will try to install files for the 114 <emphasis>x86_64-efi</emphasis> target, but those files 115 have not been installed in <xref linkend="chapter-building-system"/>. 116 If this is the case, add <option>--target i386-pc</option> to the 117 command above.</para> 188 118 </note> 189 119 -
chapter10/kernel.xml
r04ca2a7 rceb61b9 165 165 Pseudo filesystems ---> 166 166 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen> 167 168 <para>Enable some additional features if you are building a 64-bit 169 system. If you are using menuconfig, enable them in the order of 170 <parameter>CONFIG_PCI_MSI</parameter> first, then 171 <parameter>CONFIG_IRQ_REMAP</parameter>, at last 172 <parameter>CONFIG_X86_X2APIC</parameter> because an option only 173 shows up after its dependencies are selected.</para> 174 175 <screen role="nodump">Processor type and features ---> 176 [*] Support x2apic [CONFIG_X86_X2APIC] 177 Device Drivers ---> 178 [*] PCI Support ---> [CONFIG_PCI] 179 [*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI] 180 [*] IOMMU Hardware Support ---> [CONFIG_IOMMU_SUPPORT] 181 [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen> 167 182 </note> 168 183 … … 273 288 </varlistentry> 274 289 290 <varlistentry> 291 <term><parameter>Support x2apic</parameter></term> 292 <listitem> 293 <para>Support running the interrupt controller of 64-bit x86 294 processors in x2APIC mode. x2APIC may be enabled by firmware on 295 64-bit x86 systems, and a kernel without this option enabled will 296 panic on boot if x2APIC is enabled by firmware. This option has 297 has no effect, but also does no harm if x2APIC is disabled by the 298 firmware.</para> 299 </listitem> 300 </varlistentry> 301 275 302 </variablelist> 276 303 … … 327 354 the filename should be <emphasis>vmlinuz</emphasis> to be compatible with 328 355 the automatic setup of the boot process described in the next section. The 329 following command assumes an ARM64architecture:</para>330 331 <screen><userinput remap="install">cp -iv arch/ arm64/boot/Image /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>356 following command assumes an x86 architecture:</para> 357 358 <screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen> 332 359 333 360 <para><filename>System.map</filename> is a symbol file for the kernel. -
general.ent
r04ca2a7 rceb61b9 92 92 <!ENTITY test-results "&lfs-root;lfs/build-logs/&generic-version;/"> 93 93 <!ENTITY secadv "&lfs-root;lfs/advisories/"> 94 <!ENTITY min-kernel "3. 7">94 <!ENTITY min-kernel "3.2"> 95 95 <!-- 96 96 <!ENTITY patches-rootd "&lfs-root;patches/lfs/&generic-versiond;/"> -
git-version.sh
r04ca2a7 rceb61b9 49 49 50 50 sha="$(git describe --abbrev=1)" 51 rev= arm64-$(echo "$sha" | sed 's/-g[^-]*$//')51 rev=$(echo "$sha" | sed 's/-g[^-]*$//') 52 52 version="$rev" 53 53 versiond="$rev-systemd" -
prologue/architecture.xml
r04ca2a7 rceb61b9 11 11 <title>LFS Target Architectures</title> 12 12 13 <para>The target architectures of this LFS edition are ARM64 (sometimes 14 called AArch64) CPUs. On the other hand, the instructions in this book may 15 work on 32-bit ARM CPUs with some modifications. To build a system that 16 utilizes one of these CPUs, the main prerequisite, in addition to those on 17 the next page, is an existing Linux system such as an earlier LFS 18 installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that 19 targets the architecture that you have.</para> 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 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 other distribution 19 that targets the architecture that you have. Also 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> 20 22 21 <para>The build results from this LFS edition is considered a 22 <quote>pure</quote> 64-bit system. That is, it supports 64-bit executables 23 only. Building a <quote>multi-lib</quote> system requires compiling many 23 <para>For building LFS, the gain of building on a 64-bit system 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 is 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 largely sufficient. On the other 35 hand, several packages in BLFS now need more than 4GB of RAM to be built 36 and/or to run, so that if you plan to use LFS as a desktop, the LFS authors 37 recommend building on a 64-bit system.</para> 38 39 <para>The default 64-bit build that results from LFS is considered 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 24 42 applications twice, once for a 32-bit system and once for a 64-bit system. 25 43 This is not directly supported in LFS because it would interfere with the … … 27 45 straightforward base Linux system. Some LFS/BLFS editors maintain a fork 28 46 of LFS for multilib, which is accessible at <ulink 29 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But 30 the multilib edition is for x86_64, and multilib is an advanced topic 31 anyway.</para> 47 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it 48 is an advanced topic.</para> 32 49 33 50 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.