Changeset 295e337

Timestamp:

11/26/2022 08:27:58 AM (22 months ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/update-glibc

Children:

da6e70f

Parents:

aea16f6

Message:

Add note and warning about /usr/lib64

Files:

• chapter04/creatingminlayout.xml (modified) (1 diff)
• chapter07/creatingdirs.xml (modified) (1 diff)

chapter04/creatingminlayout.xml

@@ -40 +40 @@
 <screen><userinput>mkdir -pv $LFS/tools</userinput></screen>
 
+  <note>
+    <para>
+      LFS editors have deliberately decided not to use a
+      <filename class="directory">/usr/lib64</filename> directory.  Several
+      steps are taken so that the toolchain does not use it. If for any
+      reason this directory appears (either because you made an error in
+      following the instructions, or because you install a binary package that
+      creates it after finishing LFS), it may break the instructions given in
+      the book. You should often ensure that this directory is non-existent.
+    </para>
+  </note>
+
 </sect1>

chapter07/creatingdirs.xml

@@ -69 +69 @@
     directories, if you wish.  </para>
 
+  <warning>
+    <para>
+      The FHS does not enforce the existence of the directory
+      <filename class="directory">/usr/lib64</filename>, and the LFS editors
+      have decided not to use it. For the instructions in LFS and BLFS to work,
+      it is imperative that this directory be non-existent. You should often
+      check that it does not exist, because it is easy to inadvertently
+      create it, which will likely break your system.
+    </para>
+  </warning>
+
   </sect2>