On Sat, Mar 4, 2017 at 6:27 PM, Linus Lüssing <linus.luess...@c0d3.blue> wrote: >> 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 >
Thanks for the extensive testing! > 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? The build logs are publicly available, for this build[1] the versions used were: binutils_2.25-8 gcc-4.9_4.9.2-19 [1] https://buildd.debian.org/status/fetch.php?pkg=sbc&arch=armhf&ver=1.3-1&stamp=1433137735&raw=0 -- Saludos, Felipe Sateler