On Sat, Jun 17, 2006 at 01:44:34PM -0400, Mike Frysinger wrote: > On Saturday 17 June 2006 13:28, Harald van Dijk wrote: > > On Sat, Jun 17, 2006 at 01:15:58PM -0400, Mike Frysinger wrote: > > > On Saturday 17 June 2006 06:17, Luca Barbato wrote: > > > > Long term solution: > > > > 1- check your new package for aliasing compliance, and if you have time > > > > fix it in the code or in the makefile, if you haven't append > > > > -fno-strict-aliasing to the cflags and maybe send a notice about it > > > > upstream > > > > > > > > 2- append -fno-strict-aliasing to every source known to have such > > > > issue. > > > > > > 3 - include checking in portage > > > http://bugs.gentoo.org/111436 > > > > Would this make builds fail by default, or would it provide a hook for > > the user to allow builds to fail if specific conditions are matched ? > > right now such behavior is not defined > > i would lean on the FEATURES=stricter setting though to control warn/die > behavior
One reason I asked was because you'd have to force LC_ALL=C to make that work, unless you want to check for every translation of the warning. Another, as said earlier already, is that the warning is given for valid code too sometimes, but as long as it's possible to state in the ebuild that the warnings are safe to ignore for that package, I guess that's okay. -- gentoo-dev@gentoo.org mailing list
