Hi,
I just noticed that the S/390 arch maintainer in upstream glibc has pushed the patch to revert the ABI breakage he had introduced in 2.19. This will hit rawhide next week (and f21 a bit later), so please let me know if I can provide any extra assistance with this or if any particular day or time is convenient for the rebase.
Siddhesh
On Fri, 1 Aug 2014 00:19:08 +0530 Siddhesh Poyarekar siddhesh@redhat.com wrote:
Hi,
I just noticed that the S/390 arch maintainer in upstream glibc has pushed the patch to revert the ABI breakage he had introduced in 2.19. This will hit rawhide next week (and f21 a bit later), so please let me know if I can provide any extra assistance with this or if any particular day or time is convenient for the rebase.
oh, that's actually very bad news, we have no mean to rebuild everything just for s390, all rebuilds must be done first in primary. So the next rebuild can happen for F-22 unless primary decides to do an additional mass rebuild after the new glibc lands just for us. Isn't there a way how to make the revert compatible with the version we have now? I think we can't ship glibc in Fedora that would maintain different ABI than all other distros, or could we?
Dan
On Thu, Jul 31, 2014 at 09:08:57PM +0200, Dan Horák wrote:
oh, that's actually very bad news, we have no mean to rebuild everything just for s390, all rebuilds must be done first in primary.
Ugh, that sucks.
So the next rebuild can happen for F-22 unless primary decides to do an additional mass rebuild after the new glibc lands just for us.
A mass rebuild is probably the best option. I guess we could wait till there either is another reason to do an additional mass rebuild. If that doesn't happen till 2.20 is released, then we request a mass rebuild in primary when 2.20 is released.
Either way, a mass rebuild seems inevitable, unless Carlos has a better idea.
I assume a mass rebuild in rawhide is easier to request?
Isn't there a way how to make the revert compatible with the version we have now?
That would mean dropping that patch (i.e. reverting the revert), which makes us incompatible with other distros.
I think we can't ship glibc in Fedora that would maintain different ABI than all other distros, or could we?
I'm guessing no, but it's just out of conservatism and I can't think of a reason to back it. I don't think we provide any ABI guarantees for Fedora, but I am not aware of usage in s/390 to know if someone expects such consistency across distros. It might be an option to consider if primary refuses to do a mass rebuild.
The other option would be to stay frozen at this point and never really become 2.20, which is not a very nice thing, but not the end of the world either.
Siddhesh
On 07/31/2014 03:08 PM, Dan Horák wrote:
On Fri, 1 Aug 2014 00:19:08 +0530 Siddhesh Poyarekar siddhesh@redhat.com wrote:
Hi,
I just noticed that the S/390 arch maintainer in upstream glibc has pushed the patch to revert the ABI breakage he had introduced in 2.19. This will hit rawhide next week (and f21 a bit later), so please let me know if I can provide any extra assistance with this or if any particular day or time is convenient for the rebase.
oh, that's actually very bad news, we have no mean to rebuild everything just for s390, all rebuilds must be done first in primary. So the next rebuild can happen for F-22 unless primary decides to do an additional mass rebuild after the new glibc lands just for us. Isn't there a way how to make the revert compatible with the version we have now? I think we can't ship glibc in Fedora that would maintain different ABI than all other distros, or could we?
The existing F21 size of jmp_buf will be *larger* than that defined in glibc. Therefore all existing interfaces that accept *smaller* jmp_buf (all of them in glibc) will just work. However, mixing ABIs between old and new modules will still have the normal structure size incompatibility.
There is no way make it compatible. IBM made a mistake, that mistake is now being corrected. Mass rebuilds are the only way this can be fixed 100% for s390. Alternatively rebuilding perl and the perl modules should fix the biggest problems (my suggested course of action).
Any distribution based on glibc 2.19 has what is considered an "invalid ABI" for s390. They will not be compatible with the corrected ABI in 2.20. We want to move to the corrected ABI for s390.
Given that F20 is based on 2.18, and F21 is based on 2.20, it is only rawhide that ever saw 2.19, and therefore we should have the corrected ABI to ensure we are compatible with other distributions that use s390.
Cheers, Carlos.
-
Carlos O'Donell -
Dan Horák -
Siddhesh Poyarekar