> Are you sure it's definitely related to the gcc version? Did you actually
> try rebuilding with gcc-4.9 on the target machine?
>
> The thing is that assembly code is not interpreted by gcc but by the assembler
> which is part of the binutils package. Since binutils is updated
> in Debian very often, it may be well related to a bug in binutils.
I didn't try from a chroot, but tried 2.28 as you suggested as
well as a few downgraded versions, which all failed:
binutils 2.28-1 -> not
binutils 2.27.51.20161220-1
binutils 2.27-9 -> not working
binutils 2.26-1 -> not working
binutils 2.26.1-1 -> not working
binutils 2.26-12 -> not working
I also tried downgrading gcc-6, which didn't help either:
gcc 6.0.1-2
What worked then:
* gcc 4.9.4-2 + binutils 2.26.1-1
* gcc 4.9.4-2 + binutils 2.28-1
Not really familiar with how binaries get created or uploaded in
Debian, but is it possible to determine the gcc + binutils
versions with which libsbc 1.3-1 and 1.3-1+b2 were created? Just
to double check whether the official uploads were indeed created
with gcc-4.9 for libsbc 1.3-1 and gcc-5/gcc-6 for 1.3-1+b2?
Regards, Linus
PS: All those tests above just with a plain
"$ CC=gcc-{4.9,6} dpkg-buildpackage -us -uc", so with the default
hardening flags.
