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

2017-02-02 Thread Steve McIntyre
On Thu, Feb 02, 2017 at 02:42:26PM +0100, Jens Reyer wrote: >On 02/02/2017 02:30 PM, Steve McIntyre wrote: >> Dropping the -nostdlib argument to the gcc call inside sonames2elf >> makes a difference - it'll add libc6 to the mix and force the output >> to match the system you're building for. You ma

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

2017-02-02 Thread Steve McIntyre
Hi, On Thu, Feb 02, 2017 at 05:10:14AM +0100, Guillem Jover wrote: >On Wed, 2017-02-01 at 15:34:04 +, Steve McIntyre wrote: >> >> Please don't go down that route, the ABI flags are intended to save >> people from that. I'm curious what's going wrong with libgsm1 here >> such that we're not se

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

2017-02-02 Thread Jens Reyer
On 02/02/2017 02:30 PM, Steve McIntyre wrote: > Dropping the -nostdlib argument to the gcc call inside sonames2elf > makes a difference - it'll add libc6 to the mix and force the output > to match the system you're building for. You may then need to filter > out the libc6 entry afterwards, but that

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

2017-02-02 Thread Steve McIntyre
On Wed, Feb 01, 2017 at 05:03:13PM +0100, Jens Reyer wrote: >On 02/01/2017 04:34 PM, Steve McIntyre wrote: >> >> Please don't go down that route, the ABI flags are intended to save >> people from that. I'm curious what's going wrong with libgsm1 here >> such that we're not seeing consistent ABI fl

Re: 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

Re: 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 do

Re: 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 >> sonames2elf

Re: 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: >> https://buildd.debi

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

2017-01-31 Thread Guillem Jover
Hi! On Tue, 2017-01-31 at 22:44:36 +, James Cowgill wrote: > Package: dpkg > Version: 1.18.21 > Severity: serious > X-Debbugs-CC: debian-arm@lists.debian.org > [Disclaimer: I'm not an ARM porter and I don't really know much about > the ARM psABI] > > The new ABI mismatch detector seems to be

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

2017-01-31 Thread James Cowgill
Package: dpkg Version: 1.18.21 Severity: serious X-Debbugs-CC: debian-arm@lists.debian.org Hi, [Disclaimer: I'm not an ARM porter and I don't really know much about the ARM psABI] The new ABI mismatch detector seems to be a bit too strict on armel and armhf. The detector forces the ELF_FLAG_ARM_