Changeset c0c616a
- Timestamp:
- 08/19/2020 03:31:33 PM (3 years ago)
- Branches:
- 10.0, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/git-transition, xry111/glibc-2.34, xry111/glibc-2.37, xry111/kcfg-revise, xry111/lfs-next, xry111/pip3, xry111/queue-11.3, xry111/rust-wip-20221008, xry111/tester-nohack, xry111/usr-move
- Children:
- 45d8933
- Parents:
- fe4f1ad
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
rfe4f1ad rc0c616a 390 390 from /bin to /tools, create the tester user with the uid of 391 391 the tty owner, run the bash tests with su << EOF, and 392 explicit ely defining stdin (with help from thomas and bdubbs).</para>392 explicitly defining stdin (with help from thomas and bdubbs).</para> 393 393 </listitem> 394 394 </itemizedlist> -
chapter02/stages.xml
rfe4f1ad rc0c616a 69 69 <para>A few operations, from <quote>Changing Ownership</quote> to 70 70 <quote>Entering the Chroot Environment</quote> must be done as the 71 root user, with the LFS envir nment variable set for the root user.</para>71 root user, with the LFS environment variable set for the root user.</para> 72 72 </listitem> 73 73 -
chapter04/settingenviron.xml
rfe4f1ad rc0c616a 162 162 user's environment in ways that can affect the building of critical LFS 163 163 packages. To make sure the <systemitem class="username">lfs</systemitem> 164 user's env ronment is clean, check for the164 user's environment is clean, check for the 165 165 presence of <filename>/etc/bash.bashrc</filename> and, if present, move it 166 166 out of the way. As the <systemitem class="username">root</systemitem> -
chapter06/bash.xml
rfe4f1ad rc0c616a 75 75 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen> 76 76 77 <para>Move the ex cutable to where it is expected:</para>77 <para>Move the executable to where it is expected:</para> 78 78 79 79 <screen><userinput remap="install">mv $LFS/usr/bin/bash $LFS/bin/bash</userinput></screen> -
chapter06/findutils.xml
rfe4f1ad rc0c616a 58 58 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen> 59 59 60 <para>Move the ex cutable to its final expected location:</para>60 <para>Move the executable to its final expected location:</para> 61 61 62 62 <screen><userinput remap="install">mv -v $LFS/usr/bin/find $LFS/bin -
chapter06/gcc-pass2.xml
rfe4f1ad rc0c616a 124 124 <para>This option is automatically enabled when building a native 125 125 compiler with a native compiler on x86. But here, we build with 126 a cross compiler, so we need to explicit ely set this option.</para>126 a cross compiler, so we need to explicitly set this option.</para> 127 127 </listitem> 128 128 </varlistentry> -
chapter06/gzip.xml
rfe4f1ad rc0c616a 56 56 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen> 57 57 58 <para>Move the ex cutable to its final expected location:</para>58 <para>Move the executable to its final expected location:</para> 59 59 60 60 <screen><userinput remap="install">mv -v $LFS/usr/bin/gzip $LFS/bin</userinput></screen> -
chapter06/introduction.xml
rfe4f1ad rc0c616a 25 25 together with building as root, may render your computer unusable. 26 26 This whole chapter must be done as user <systemitem 27 class="username">lfs</systemitem>, with the enviro ment as described in27 class="username">lfs</systemitem>, with the environment as described in 28 28 <xref linkend="ch-preps-settingenviron"/>.</para> 29 29 -
chapter08/coreutils.xml
rfe4f1ad rc0c616a 128 128 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"</userinput></screen> 129 129 130 <para>The test-getlogin test is known to fail in the LFS chroot env ronment.</para>130 <para>The test-getlogin test is known to fail in the LFS chroot environment.</para> 131 131 132 132 <para>Remove the temporary group:</para> -
chapter08/revisedchroot.xml
rfe4f1ad rc0c616a 51 51 52 52 <para>There are also several files installed in the /usr/lib and /usr/libexec 53 directories with a file name exten tion of .la. These are "libtool archive"53 directories with a file name extension of .la. These are "libtool archive" 54 54 files. As already said, they are only useful when linking with static 55 55 libraries. They are unneeded, and potentially harmful, when using dynamic -
part3intro/toolchaintechnotes.xml
rfe4f1ad rc0c616a 323 323 <command>cc</command> when the host is the same as the target, but is 324 324 different from the build system. This is why 325 <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is put explicit ely into325 <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is put explicitly into 326 326 the configure options.</para> 327 327
Note:
See TracChangeset
for help on using the changeset viewer.