Changeset 295e337


Ignore:
Timestamp:
11/26/2022 08:27:58 AM (4 months ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.3, 11.3-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/glibc-2.37, xry111/kcfg-revise
Children:
da6e70f
Parents:
aea16f6
Message:

Add note and warning about /usr/lib64

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • chapter04/creatingminlayout.xml

    raea16f6 r295e337  
    4040<screen><userinput>mkdir -pv $LFS/tools</userinput></screen>
    4141
     42  <note>
     43    <para>
     44      LFS editors have deliberately decided not to use a
     45      <filename class="directory">/usr/lib64</filename> directory.  Several
     46      steps are taken so that the toolchain does not use it. If for any
     47      reason this directory appears (either because you made an error in
     48      following the instructions, or because you install a binary package that
     49      creates it after finishing LFS), it may break the instructions given in
     50      the book. You should often ensure that this directory is non-existent.
     51    </para>
     52  </note>
     53
    4254</sect1>
  • chapter07/creatingdirs.xml

    raea16f6 r295e337  
    6969    directories, if you wish.  </para>
    7070
     71  <warning>
     72    <para>
     73      The FHS does not enforce the existence of the directory
     74      <filename class="directory">/usr/lib64</filename>, and the LFS editors
     75      have decided not to use it. For the instructions in LFS and BLFS to work,
     76      it is imperative that this directory be non-existent. You should often
     77      check that it does not exist, because it is easy to inadvertently
     78      create it, which will likely break your system.
     79    </para>
     80  </warning>
     81
    7182  </sect2>
    7283
Note: See TracChangeset for help on using the changeset viewer.