Distributions still suffering from s390 ABI change problems.
Carlos O'Donell
carlos@redhat.com
Mon Jul 14 16:51:00 GMT 2014
On 07/14/2014 03:25 AM, David Miller wrote:
> From: Aurelien Jarno <aurelien@aurel32.net>
> Date: Mon, 14 Jul 2014 09:22:28 +0200
>
>> We can continue handling this ABI change by rebuilding all packages
>> dependind on libpng, but I am afraid that embedding a jmp_buf in a
>> structure is not that uncommon and that we are going to discover
>> more affected packages.
>
> This is a really serious mess.
There was no other way around this, and our tooling sucks for detecting
mixed ABI usage and telling users how to fix it.
It is documented in the 2.19 release notes here:
https://sourceware.org/glibc/wiki/Release/2.19#Packaging_Changes
IBM knew this was a serious mess, but for reasons of hardware enablement
the size had to be extended. There are backwards compatible versions of
the functions that use these structures, but that's not much consolation
when we know the structure size is embedded in other structures.
For RHEL we've had to make some very special statements to our customers
regarding this transition, and we had to rebuild packages to fix this
issues.
Debian suffers the most because they don't do mass rebuilds.
It is a mess, but it's less mess than might happen later.
Cheers,
Carlos.
More information about the Libc-alpha
mailing list