From: Sergei Trofimovich <slyich@gmail.com>
To: Ian Kumlien <pomac@demius.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: -U_FORTIFY_SOURCE before -D
Date: Sat, 9 Feb 2013 21:02:06 +0300 [thread overview]
Message-ID: <20130209210206.66e2b886@sf> (raw)
In-Reply-To: <1360366221-22703-1-git-send-email-pomac@demius.net>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Sat, 9 Feb 2013 00:30:21 +0100
Ian Kumlien <pomac@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).
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.
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-09 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:30 [PATCH] Btrfs-progs: -U_FORTIFY_SOURCE before -D Ian Kumlien
2013-02-09 18:02 ` Sergei Trofimovich [this message]
2013-02-09 18:57 ` Ian Kumlien
2013-02-09 22:06 ` Sergei Trofimovich
2013-02-09 22:33 ` Ian Kumlien
2013-02-12 14:18 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130209210206.66e2b886@sf \
--to=slyich@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pomac@demius.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.