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

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

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

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