Author: pierre
Date: Wed May 6 06:02:47 2020
New Revision: 11837
Log:
Avoid having /bin in lfs' PATH if the build distro has merged
/bin and /usr/bin
Modified:
branches/cross-chap5/chapter04/settingenviron.xml
Modified: branches/cross-chap5/chapter04/settingenviron.xml
==============================================================================
--- branches/cross-chap5/chapter04/settingenviron.xml Wed May 6 05:59:54
2020 (r11836)
+++ branches/cross-chap5/chapter04/settingenviron.xml Wed May 6 06:02:47
2020 (r11837)
@@ -43,7 +43,9 @@
LFS=/mnt/lfs
LC_ALL=POSIX
LFS_TGT=$(uname -m)-lfs-linux-gnu
-PATH=$LFS/tools/bin:/bin:/usr/bin
+PATH=/usr/bin
+if [ ! -l /bin ]; then PATH=/bin:$PATH; fi
+PATH=$LFS/tools/bin:$PATH
export LFS LC_ALL LFS_TGT PATH</literal>
EOF</userinput></screen>
@@ -108,14 +110,36 @@
</varlistentry>
<varlistentry>
- <term><parameter>PATH=$LFS/tools/bin:/bin:/usr/bin</parameter></term>
+ <term><parameter>PATH=/usr/bin</parameter></term>
+ <listitem>
+ <para>Many modern linux distributions have merged <filename
+ class="directory">/bin</filename> and <filename
+ class="directory">/usr/bin</filename>. When this is the case, the standard
+ <envar>PATH</envar> variable needs just to be set to <filename
+ class="directory">/usr/bin/</filename> for the <xref
+ linkend="chapter-temporary-tools"/> environment. When this is not the
+ case, the following line adds <filename class="directory">/bin</filename>
+ to the path.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><parameter>if [ ! -l /bin ]; then PATH=/bin:$PATH;
fi</parameter></term>
+ <listitem>
+ <para>If <filename class="directory">/bin</filename> is not a symbolic
+ link, then it has to be added to the <envar>PATH</envar> variable.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><parameter>PATH=$LFS/tools/bin:$PATH</parameter></term>
<listitem>
<para>By putting <filename class="directory">$LFS/tools/bin</filename> ahead
of the
- standard <envar>PATH</envar>, all the programs installed in <xref
- linkend="chapter-temporary-tools"/> are picked up by the shell immediately
after
- their installation. This, combined with turning off hashing, limits the risk
- that old programs are used from the host when the same programs are
available in
- the Chapter 5 environment.</para>
+ standard <envar>PATH</envar>, the cross-compiler installed at the beginning
+ of <xref linkend="chapter-temporary-tools"/> is picked up by the shell
+ immediately after its installation. This, combined with turning off hashing,
+ limits the risk that the compiler from the host be used instead of the
+ cross-compiler.</para>
</listitem>
</varlistentry>
--
http://lists.linuxfromscratch.org/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
