| 1 |
On Friday, 21 June 2019 08:56:34 BST Kai Peter wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I couldn't find an appropriate documentation for this, so it is not |
| 5 |
> clear to me how a __no-multilib__ layout looks like with 17.1 profiles. |
| 6 |
> All for amd64. |
| 7 |
> |
| 8 |
> With 17.0-no-multilib '/lib' is a symlink to '/lib64'. For |
| 9 |
> 17.1-no-multilib I see 4 possibilities: |
| 10 |
> |
| 11 |
> 1. no change |
| 12 |
> |
| 13 |
> 2. both '/lib' and '/lib64' are directories (don't expect this, but it's |
| 14 |
> possible) |
| 15 |
> |
| 16 |
> 3. 'lib64' is a symlink to '/lib' |
| 17 |
> |
| 18 |
> 4. only one folder '/lib' __OR__ 'lib64' exists |
| 19 |
> |
| 20 |
> With an eye to lfs I would expect to have one '/lib' only. Did anybody |
| 21 |
> the switch already and can tell me what happens? |
| 22 |
> |
| 23 |
> Thanks |
| 24 |
> Kai |
| 25 |
|
| 26 |
On my amd64 no-multilib system there is of course no /lib32 or /usr/lib32. |
| 27 |
|
| 28 |
There are: |
| 29 |
|
| 30 |
$ ls -ld /lib* |
| 31 |
drwxr-xr-x 11 root root 4096 Jun 7 13:23 /lib |
| 32 |
drwxr-xr-x 8 root root 12288 Jun 14 23:42 /lib64 |
| 33 |
|
| 34 |
and |
| 35 |
|
| 36 |
$ ls -ld /usr/lib* |
| 37 |
drwxr-xr-x 21 root root 4096 Jun 15 00:06 /usr/lib |
| 38 |
drwxr-xr-x 104 root root 159744 Jun 19 08:15 /usr/lib64 |
| 39 |
drwxr-xr-x 18 root root 4096 Jun 14 23:54 /usr/libexec |
| 40 |
|
| 41 |
all of which as you can see are real directories. |
| 42 |
-- |
| 43 |
Regards, |
| 44 |
Mick |
Archives