On Sun, Nov 15, 2015 at 08:10:50PM +0000, Chris Knadle wrote: > Kurt Roeckx: > > On Sun, Nov 15, 2015 at 08:00:57AM +0000, Chris Knadle wrote: > >> I'd like to try building openssl_1.0.2d-1 with gcc-4.9 to see if the > >> behavior change was due to gcc-5 -- if there's an easy way to specify that > >> please let me know. > > > > If you edit the Configure file, for instance the debian-amd64 > > line, it has the compiler for that target in it. > > > > Note that the debian-amd64 line comes from the > > debian-targets.patch. > > Thanks, that was helpful. > > ... Huh. Rebuilding openssl_1.0.2d-1 with gcc-4.9 and using it to build > mumble_1.2.10-2 with g++-5, the result works fine. So it seems it was > simply the switch to gcc-5 that changed this behavior. > > On the one hand one could call this a regression since it breaks something > that worked before, and on the other hand it caught a bug in the code in > mumble that nobody knew it had. This therefore leaves a question as to > whether to consider this is a bug or a feature of gcc-5. Probably both.
I'm not sure what to make of this. I find it strange the a change in the compiler can have something like that as effect. Kurt
