Handling s390 libc ABI change in Debian

2014-07-14 Thread Aurelien Jarno
Hi all, glibc 2.19 has changed the libc ABI on s390, more specifically the setjmp/longjmp functions [1] [2]. Symbol versioning is used to handle some cases, but it doesn't work when a jmp_buf variable is embedded into a structure, as it changes the size of the structure. The result is that mixing

Re: Handling s390 libc ABI change in Debian

2014-07-14 Thread Carlos O'Donell
On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno wrote: > glibc 2.19 has changed the libc ABI on s390, more specifically the > setjmp/longjmp functions [1] [2]. Symbol versioning is used to handle > some cases, but it doesn't work when a jmp_buf variable is embedded > into a structure, as it change

Re: Handling s390 libc ABI change in Debian

2014-07-14 Thread Aurelien Jarno
On Mon, Jul 14, 2014 at 11:14:42PM -0400, Carlos O'Donell wrote: > On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno wrote: > > glibc 2.19 has changed the libc ABI on s390, more specifically the > > setjmp/longjmp functions [1] [2]. Symbol versioning is used to handle > > some cases, but it doesn't

Re: Handling s390 libc ABI change in Debian

2014-07-14 Thread Paul Wise
On Tue, Jul 15, 2014 at 1:18 PM, Aurelien Jarno wrote: > It's a huge work for Debian, maybe not for other distribution, as it > basically means we have to rebootstrap everything. This includes manual > bootstrapping of self-dependent languages (haskell, gnat, ...) and > manual handling of some dep

Re: Handling s390 libc ABI change in Debian

2014-07-15 Thread Philipp Kern
On Tue, Jul 15, 2014 at 07:18:39AM +0200, Aurelien Jarno wrote: > I can follow up with a list affected packages, but we are slowly > discovering them one by one, so it might takes time. So far we have: > > * Mixing modules/libraries built with pre-2.19 and 2.19 libc > - perl > - libpng > > * Usi

Re: Handling s390 libc ABI change in Debian

2014-07-15 Thread Carlos O'Donell
On Tue, Jul 15, 2014 at 1:18 AM, Aurelien Jarno wrote: > On Mon, Jul 14, 2014 at 11:14:42PM -0400, Carlos O'Donell wrote: >> On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno wrote: >> > glibc 2.19 has changed the libc ABI on s390, more specifically the >> > setjmp/longjmp functions [1] [2]. Symbol

Re: Handling s390 libc ABI change in Debian

2014-07-15 Thread Aurelien Jarno
On Tue, Jul 15, 2014 at 09:21:30AM +0200, Philipp Kern wrote: > On Tue, Jul 15, 2014 at 07:18:39AM +0200, Aurelien Jarno wrote: > > I can follow up with a list affected packages, but we are slowly > > discovering them one by one, so it might takes time. So far we have: > > > > * Mixing modules/lib

Re: Handling s390 libc ABI change in Debian

2014-07-15 Thread Aurelien Jarno
On Tue, Jul 15, 2014 at 03:49:04AM -0400, Carlos O'Donell wrote: > On Tue, Jul 15, 2014 at 1:18 AM, Aurelien Jarno wrote: > > On Mon, Jul 14, 2014 at 11:14:42PM -0400, Carlos O'Donell wrote: > >> On Mon, Jul 14, 2014 at 4:36 PM, Aurelien Jarno wrote: > >> > glibc 2.19 has changed the libc ABI on

Re: Handling s390 libc ABI change in Debian

2014-07-28 Thread Emilio Pozuelo Monfort
On 14/07/14 22:36, Aurelien Jarno wrote: > Hi all, > > glibc 2.19 has changed the libc ABI on s390, more specifically the > setjmp/longjmp functions [1] [2]. Symbol versioning is used to handle > some cases, but it doesn't work when a jmp_buf variable is embedded > into a structure, as it changes