From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Euan Harris <euan.harris@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian.Campbell@citrix.com, Wen Congyang <wency@cn.fujitsu.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2] Fix building error
Date: Wed, 4 Feb 2015 17:42:01 +0100 [thread overview]
Message-ID: <20150204164201.GA14456@aepfle.de> (raw)
In-Reply-To: <54D24AB5020000780005CEBE@mail.emea.novell.com>
On Wed, Feb 04, Jan Beulich wrote:
> I also checked Python, and they also seem to have been enabling
> _FORTIFY_SOURCE forever. Consequently, with the previously suggested
> patches not having found acceptance, how about
I'm sure python just carries the CFLAGS used for its build, so that
other python related code can use the very same CFLAGS. IMO that is
valid. Since the whole distro is built with those CFLAGS via
RPM_OPT_FLAGS it will end up also in python.
I wonder, is it just SUSE and Fedora that use _FORTIFY_SOURCE in global
CFLAGS?
Olaf
prev parent reply other threads:[~2015-02-04 16:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 10:39 [PATCH] libxl/Makefile: Don't optimize debug builds; add macro debugging information Euan Harris
2014-12-01 11:43 ` Ian Campbell
2014-12-01 11:55 ` Euan Harris
2014-12-01 12:12 ` Ian Campbell
2014-12-01 14:21 ` [PATCH v2] tools/Rules.mk: " Euan Harris
2015-01-08 17:16 ` Ian Campbell
2015-01-12 16:42 ` Ian Campbell
2015-01-13 5:52 ` Wen Congyang
2015-01-13 10:11 ` Ian Campbell
2015-01-13 10:38 ` Wen Congyang
2015-01-13 11:17 ` Wen Congyang
2015-01-13 11:30 ` Ian Campbell
2015-01-15 3:38 ` Wen Congyang
2015-01-15 3:39 ` [PATCH] Fix building error Wen Congyang
2015-01-15 7:57 ` Olaf Hering
2015-01-15 9:04 ` Wen Congyang
2015-01-15 9:21 ` Olaf Hering
2015-01-15 9:28 ` Wen Congyang
2015-01-15 9:33 ` [PATCH v2] " Wen Congyang
2015-01-15 11:26 ` Ian Jackson
2015-01-19 15:23 ` Ian Campbell
2015-01-20 2:21 ` Wen Congyang
2015-01-20 10:18 ` Ian Campbell
2015-01-20 10:39 ` Wen Congyang
2015-01-20 12:47 ` Olaf Hering
2015-01-23 11:34 ` Julien Grall
2015-02-04 15:37 ` Jan Beulich
2015-02-04 15:43 ` Ian Jackson
2015-02-04 16:02 ` Jan Beulich
2015-02-04 16:10 ` Ian Jackson
2015-02-04 16:42 ` Olaf Hering [this message]
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=20150204164201.GA14456@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=euan.harris@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
/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.