Le 30/01/2013 18:02, Andrew Wafaa a écrit :
On 30 January 2013 16:34, Alexander Graf
wrote: On 30.01.2013, at 17:32, Guillaume Gardet wrote:
Hi,
I was wondering if we want to use /lib64 and /usr/lib64 for AArch64 or use /lib and /usr/lib.
It seems Fedora uses lib64 whereas linaro uses lib.
Debian seems to use a symlink so that lib and lib64 are the same.
Some people discussed about that on cross-distro list some times ago; AArch64 triplet thread: http://lists.linaro.org/pipermail/cross-distro/2012-November/thread.html
It seems Fedora is right using lib64 convention. Should we use it also? It is better to decide now since aarch64 is at an early stage. I think it makes sense to follow Fedora here. It will ensure that we maintain compatibility at least within rpm based distros.
We should indeed use lib64, not only to maintain compatibility with the likes of Fedora, but it also simplifies things across architectures. If I'm not totally mistaken, Debian do the symlink dance as they use multiarch so are somewhat different.
Ok. And what about CANONCOLOR parameter for RPM: # The default transaction color. This value is a set of bits to # determine file and dependency affinity for this arch. # 0 uncolored (i.e. use only arch as install hint) # 1 Elf32 permitted # 2 Elf64 permitted Fedora uses code 2 (Elf64 only) but AArch64 should be able to run Elf32 also, so code 3 (1+2) should be better. What do you think about that? Regards, Guillaume
Regards,
Andy
-- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org