mlfs question

"Mark Park" ([email protected] via lfs-support Mailing List) <[email protected]> Thu, 17 Apr 2025 21:21:49 -0500
Newsgroups gmane.linux.lfs.support
Message-ID <CANOUG1Gqaz3d5h3daQq-79Mg2K_bnLuAnQHXYPG0nXxW0SibBg@mail.gmail.com>
I'm in chapter 4.2 setting up the limited directory layout and the page
seems to have conflicting information. ( see
https://linuxfromscratch.org/~thomas/multilib-systemd-m32/chapter04/creatingminlayout.html
)

It has this command which creates a lib64 directory in the root of /mnt/lfs:

case $(uname -m) in
  x86_64) mkdir -pv $LFS/lib64 ;;
esac

Followed up with the following note:

Note

The LFS editors have deliberately decided not to use a /usr/lib64
directory. Several steps are taken to be sure the toolchain will not use
it. If for any reason this directory appears (either because you made an
error in following the instructions, or because you installed a binary
package that created it after finishing LFS), it may break your system. You
should always be sure this directory does not exist.


Which implies there should not be a lib64 directory. Is this an error in
the commands or is this a leftover note from the pure 64-bit standard build?

I've paused my build for now - I can always reboot the vm and pick it up
later.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page