On 2019-06-21 10:44, Mick wrote:
On Friday, 21 June 2019 08:56:34 BST Kai Peter wrote:
Hi,
I couldn't find an appropriate documentation for this, so it is not
clear to me how a __no-multilib__ layout looks like with 17.1
profiles.
All for amd64.
With 17.0-no-multilib '/lib' is a symlink to '/lib64'. For
17.1-no-multilib I see 4 possibilities:
1. no change
2. both '/lib' and '/lib64' are directories (don't expect this, but
it's
possible)
3. 'lib64' is a symlink to '/lib'
4. only one folder '/lib' __OR__ 'lib64' exists
With an eye to lfs I would expect to have one '/lib' only. Did anybody
the switch already and can tell me what happens?
Thanks
Kai
On my amd64 no-multilib system there is of course no /lib32 or
/usr/lib32.
There are:
$ ls -ld /lib*
drwxr-xr-x 11 root root 4096 Jun 7 13:23 /lib
drwxr-xr-x 8 root root 12288 Jun 14 23:42 /lib64
and
$ ls -ld /usr/lib*
drwxr-xr-x 21 root root 4096 Jun 15 00:06 /usr/lib
drwxr-xr-x 104 root root 159744 Jun 19 08:15 /usr/lib64
drwxr-xr-x 18 root root 4096 Jun 14 23:54 /usr/libexec
all of which as you can see are real directories.
Thanks.
--
Sent with eQmail-1.10.3 beta - a fork of djb's famous qmail
