On 2018-06-27 10:54, Thanos Baloukas wrote:
On 27/06/2018 06:22 μμ, Armin K. wrote:
On 27.6.2018. 13:40, Thanos Baloukas wrote:
I can't confirm this. I install everything in destdir initially,
create
binary packages and then I install them on /.
/usr/lib64 does not exist on my system. Example packages that are
built
with meson without --libdir=/usr/lib and install their libraries in
/usr/lib are libinput libdrm and pango.
It seems to detect if /usr/lib64 exists first (and LFS does create
this as a symlink) before installing there. I do not have /usr/lib64
either, not as a symlink or a dierctory, and meson never tried to
install anything there.
Hi Armin
LFS doesn't create the /usr/lib64 symlink anymore, unless I'm missing
that.
--
Thanos
Greetings,
Yes if /usr/lib64 exists then output of meson --help will list default
as /usr/lib64. Even if a system has /lib64 it won't matter. This is a
meson matter, not LFS. Meson, as far as I'm concerned, did it right.
Even if on a 64bit system and multilib enabled, if it's pure64 bit with
just /usr/lib that'd be right. Just my 42342354352423 cents.
Sincerely,
William Harrington
--
You feel a whole lot more like you do now than you did when you used
to.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
