| 1 |
On 09/11/2011 12:50, William Hubbs wrote: |
| 2 |
|
| 3 |
> Here is what I've found in fhs [2]. |
| 4 |
> |
| 5 |
> - /lib should always exist on all architectures. |
| 6 |
> - /lib64 should only exist on amd64, ppc64, sparc64 and s390x. It |
| 7 |
> should hold 64 bit libraries, and /lib should hold 32 bit (or 31 bit |
| 8 |
> on s390x) libraries. |
| 9 |
> - /lib should hold 64 bit libraries on ia64. |
| 10 |
> - FHS mentions /lib32 but doesn't really define what goes in it, and with |
| 11 |
> the definition of when /lib64 is to be used, there doesn't seem to be a |
| 12 |
> need for /lib32. |
| 13 |
> - Also, it seems questionable that /lib is a symlink to /lib64 on |
| 14 |
> non-multilib systems. I think we should still have separate /lib and |
| 15 |
> /lib64 directories. |
| 16 |
|
| 17 |
|
| 18 |
MIPS clarification: |
| 19 |
o32 ABI (32bit) -> /lib |
| 20 |
n32 ABI (32bit w/ full access to 64bit address space/registers) -> /lib32 |
| 21 |
n64 ABI (64bit) -> /lib64 |
| 22 |
|
| 23 |
In a full-on MIPS multilib, you can have all three folders present and |
| 24 |
filled with their respective ABI libs/binaries. One ABI will dominate the |
| 25 |
system, though. Right now, that's still o32, but not for much longer. n32 |
| 26 |
will become the defacto soon, and o32 will be built only if needed (i.e. a |
| 27 |
program exhibits issues in n32 until upstream can fix). n64 is also an |
| 28 |
as-needed basis, typically where a program derives a benefit from being true |
| 29 |
64bit versus one of the other two. |
| 30 |
|
| 31 |
-- |
| 32 |
Joshua Kinard |
| 33 |
Gentoo/MIPS |
| 34 |
kumba@g.o |
| 35 |
4096R/D25D95E3 2011-03-28 |
| 36 |
|
| 37 |
"The past tempts us, the present confuses us, the future frightens us. And |
| 38 |
our lives slip away, moment by moment, lost in that vast, terrible in-between." |
| 39 |
|
| 40 |
--Emperor Turhan, Centauri Republic |
Archives