Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-01 Thread Guillem Jover
On Wed, 2017-02-01 at 15:34:04 +, Steve McIntyre wrote: > On Wed, Feb 01, 2017 at 05:08:50AM +0100, Guillem Jover wrote: > >On Tue, 2017-01-31 at 22:44:36 +, James Cowgill wrote: > >> > >> Here libgsm.so has neither HARD or SOFT flags set. Also, asking gcc to > >> generate a library which

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-01 Thread Jens Reyer
On 02/01/2017 04:34 PM, Steve McIntyre wrote: > Hey folks, > > On Wed, Feb 01, 2017 at 05:08:50AM +0100, Guillem Jover wrote: >> On Tue, 2017-01-31 at 22:44:36 +, James Cowgill wrote: >>> >>> Here libgsm.so has neither HARD or SOFT flags set. Also, asking gcc to >>> generate a library which

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-01 Thread Steve McIntyre
Hey folks, On Wed, Feb 01, 2017 at 05:08:50AM +0100, Guillem Jover wrote: >On Tue, 2017-01-31 at 22:44:36 +, James Cowgill wrote: >> >> Here libgsm.so has neither HARD or SOFT flags set. Also, asking gcc to >> generate a library which does not link against libc (this is used by >>

Bug#853793: dpkg: ABI mismatch detector is too strict on armel/armhf

2017-02-01 Thread Jens Reyer
On 02/01/2017 05:08 AM, Guillem Jover wrote: > On Tue, 2017-01-31 at 22:44:36 +, James Cowgill wrote: >> The new ABI mismatch detector seems to be a bit too strict on armel and >> armhf. Thanks to both of you for quickly handling this! >> This was first seen with wine: >>