Re: Proposal: Rethink Fedora multilib support (Take Two!)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/09/2017 03:37 PM, Dennis Gilmore wrote:

the only reason that aarch64 used /usr/lib64 was so it looked more like
 x86_64 from a user perspective, there is 64 bit arches like alpha that
use /usr/lib for their libraries.

We'll see soon what the non-multiarch layout will be for aarch64 (but hopefully not in Fedora). Maybe something like this?

/usr/lib     ARMv7/armhfp binaries
/usr/lib64   aarch64 64-bit binaries
/usr/lib32   aarch64 in ILP32 mode (32-bit binaries)

This is similar to x86_64, where the conjectured layout is:

/usr/lib     i386
/usr/lib64   x86_64 64-bit binaries
/usr/libx32  x86_64 in ILP32 (x32, 32-bit binaries)

The Debian multi-arch approach has the advantage that it provides a consistent way to determine the paths, and also a systematic way to deal with file conflicts in /usr/include.

Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux