arm softfp ABI vs hardfp in rpm world
adrian at suse.de
Mon Apr 23 18:20:27 UTC 2012
I would like to propose a change in the rpm provides/requires handling of
libs and binaries.
Right now, we use on arm the architecture to distinguish between hard and
soft fp abi.
This results to the fact that armv7l is complete incompatible to armv7hl
due to the rpm architecture compatibility list (is this true everywhere?)
This is IMHO technical wrong. For example an rpm with a static build soft-fp
binary should be installable on a hard-fp system. The kernel and the
hardware does support it and it would just run.
But furthermore this will make it also impossible later to have mixed systems.
What I like to do on openSUSE-ARM is to go the same way as i686 vs. x86_64
world did go. Declare i686 backward compatible from x86_64, but to
extent the provides and requires with an extension. So a hf binary will
still require a hf lib.
A patch for rpm which should do this is attached, but I have not tested
it, I have to admit. The reason is that want to discuss it here first,
because this has a big impact: It would suddenly make the old armv7hl rpms
not compatible anymore with the new ones.
So, I would like to here if you share my POV here in general. And secondly,
if you see a chance at all to do this switch.
I promise to take care to push such a patch to rpm upstream, if you want it.
PS: I have not evaluated how the NEON VFP world fits in here.
SUSE Linux Products GmbH
email: adrian at suse.de
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2125 bytes
Desc: not available
More information about the cross-distro