On Sun, 19 Mar 2017 18:51:00 +0100 Linus =?utf-8?Q?L=C3=BCssing?= <linus.luess...@c0d3.blue> wrote: > On Sat, Mar 04, 2017 at 07:37:36PM -0300, Felipe Sateler wrote: > > > 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 > > Aiy, ok, thanks a lot, Felipe! > > Is there anything else I could do? Was the issue reported to the > gcc folks somewhere yet or should I report it to some bugtracker of > the gcc project? > >
AFAICT, so we only have signs of arm being affected, but the arm port list have not been included on this bug. I am CC'ing them now so we are certain that they are aware of it. At the same time, has anyone reproduced this on any other architecture than arm? Thanks, ~Niels
