Re: mlfs question

On Thu, 2025-04-17 at 21:21 -0500, Mark Park wrote:
> 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?

No, the text is very clear we don't use a /usr/lib64 directory.  I.e.
there should be no $LFS/usr/lib64, and it's not related to $LFS/lib64.

Even in MLFS there shouldn't be /usr/lib64.

And even in plain x86_64 LFS /lib64 *must* exist, see
https://www.linuxfromscratch.org/lfs/faq.html#get-rid-of-lib64 for the
reason.

-- 
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University

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