From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, "Michal Privoznik" <mprivozn@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] configure: Undefine _FORTIFY_SOURCE prior using it
Date: Wed, 06 Feb 2013 16:09:22 +0100 [thread overview]
Message-ID: <51127222.1040904@redhat.com> (raw)
In-Reply-To: <20130206144956.GA22233@stefanha-thinkpad.redhat.com>
Il 06/02/2013 15:49, Stefan Hajnoczi ha scritto:
>> > I don't think that's necessary. The 2nd level is the highest one [1] or [2].
>> > It seems like in my case it's compiler who's defining the macro:
>> >
>> > $ echo "int main() {return 0;}" | gcc -D_FORTIFY_SOURCE=2 -x c -
>> > <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default]
>> > <stdin>:1:0: note: this is the location of the previous definition
>> >
>> > in which case we must undefine it. However, if the _FORTIFY_SOURCE is
>> > defined by environment, I think we should not override it. So maybe need
>> > a different approach. Anyway, with current state I cannot compile. I am using
>> > gcc version 4.7.2 (Gentoo 4.7.2 p1.3, pie-0.5.5)
> It would be nice to fix this for QEMU 1.4 but my gcc FORTIFY_SOURCE foo
> is not strong enough to know what the best approach is here.
>
> Reviews from anyone else?
I would prefer to avoid having _FORTIFY_SOURCE completely, and let
distros do it. Alternatively, tie it to a new --enable switch which
would do -U -D.
But if there is a real problem for 1.4 the patch looks good.
Paolo
next prev parent reply other threads:[~2013-02-06 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 10:15 [Qemu-trivial] [PATCH] configure: Undefine _FORTIFY_SOURCE prior using it Michal Privoznik
2013-02-01 9:54 ` [Qemu-trivial] [Qemu-devel] " Andreas Färber
2013-02-01 9:54 ` Andreas Färber
2013-02-01 15:18 ` [Qemu-trivial] " Michal Privoznik
2013-02-01 15:18 ` Michal Privoznik
2013-02-06 14:49 ` [Qemu-trivial] " Stefan Hajnoczi
2013-02-06 15:09 ` Paolo Bonzini [this message]
2013-04-23 17:18 ` Michal Privoznik
2013-04-23 17:18 ` [Qemu-devel] [Qemu-trivial] " Michal Privoznik
2013-04-24 10:00 ` [Qemu-trivial] [Qemu-devel] " Markus Armbruster
2013-04-24 10:00 ` [Qemu-devel] [Qemu-trivial] " Markus Armbruster
2013-02-06 17:05 ` [Qemu-trivial] [Qemu-devel] " Richard Henderson
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=51127222.1040904@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
/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.