tags 646334 pending clone 646334 -1 reassign -1 gcc-4.4 title -1 gcc-4.4 on m68k thinks a variable may be used uninitialized when it won't thanks
On Mon, Oct 24, 2011 at 08:02:12AM +0000, Thorsten Glaser wrote: > Steve Langasek dixit: > >This is only the correct severity for a build failure when it happens on a > >release architecture. The latest freetype package has built successfully on > >all release architectures, per <https://buildd.debian.org/freetype>. > Tell that reportbug. > I see (and disagree with, but it’s not my package) your reasoning; > would it be possible to enable -Werror only for release architectures > then? (Hey, that’s a good idea, let dpkg provide the set of release > architectures in a query.) I don't think that's a very interesting query wrt build systems (and I don't think dpkg would be an appropriate place for it to live anyway). We should only disable this on systems with the known compiler bug - i.e., on m68k and alpha, instead of on "all non-release archs". I've committed this workaround locally and will include it in my next upload (which is imminent). I'm also cloning this bug over to gcc-4.4. Is there a reason that these architectures use gcc-4.4 as the default, when all release architectures are at gcc-4.6? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
