| 1 |
Hi, |
| 2 |
|
| 3 |
I couldn't find an appropriate documentation for this, so it is not |
| 4 |
clear to me how a __no-multilib__ layout looks like with 17.1 profiles. |
| 5 |
All for amd64. |
| 6 |
|
| 7 |
With 17.0-no-multilib '/lib' is a symlink to '/lib64'. For |
| 8 |
17.1-no-multilib I see 4 possibilities: |
| 9 |
|
| 10 |
1. no change |
| 11 |
|
| 12 |
2. both '/lib' and '/lib64' are directories (don't expect this, but it's |
| 13 |
possible) |
| 14 |
|
| 15 |
3. 'lib64' is a symlink to '/lib' |
| 16 |
|
| 17 |
4. only one folder '/lib' __OR__ 'lib64' exists |
| 18 |
|
| 19 |
With an eye to lfs I would expect to have one '/lib' only. Did anybody |
| 20 |
the switch already and can tell me what happens? |
| 21 |
|
| 22 |
Thanks |
| 23 |
Kai |
| 24 |
|
| 25 |
-- |
| 26 |
Sent with eQmail-1.10.3 beta - a fork of djb's famous qmail |
Archives