On Sat, Feb 09, 2013 at 09:02:06PM +0300, Sergei Trofimovich wrote: > On Sat, 9 Feb 2013 00:30:21 +0100 > Ian Kumlien <po...@demius.net> wrote: > > > My builds are cluttered with: > > <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by > > default] > > > > Which makes it hard to tell if something breaks or not. > > > I don't know about you, but bilding with > > GCC 4.7.2 on gentoo, this is a issue. > > Unfortunately it's a gentoo specific gcc bug. I'd suggest reporting > it to bugs.gentoo.org. That -D by default breaks linux's perf as well > (due to -D_FOTIFY_SOURCE=2 -Werror in perf sources).
Is it? There is a workaround in the android build system for compilers on ubuntu. Where can i find that bug report? This is not a emerge, this is a normal system build. > Current workaround is to pass AM_CFLAGS to make: > make AM_CFLAGS=stuff_w/o_fortify_source > It's what gentoo's live ebuild does. I can't see it here in the live ebuild... > -- > > Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
