From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/qemu-xen: remove CFLAGS for qemu build
Date: Thu, 1 Mar 2012 18:53:25 +0100 [thread overview]
Message-ID: <20120301175325.GA8395@aepfle.de> (raw)
In-Reply-To: <20303.46312.444472.874775@mariner.uk.xensource.com>
On Thu, Mar 01, Ian Jackson wrote:
> Olaf Hering writes ("[Xen-devel] [PATCH] tools/qemu-xen: remove CFLAGS for qemu build"):
> > tools/qemu-xen: remove CFLAGS for qemu build
> >
> > Currently qemu-xen gets build with CFLAGS only if CFLAGS was already in
> > the environment during make invocation. If CFLAGS is in environment then
> > make will append all of the various flags specified in xen Makefiles,
> > which is then passed to qemu configure. If CFLAGS is not set, then
> > configure will use just "-O2 -g" because make does not export its own
> > CFLAGS variable.
> >
> > To make qemu-xen build consistent this change removes CFLAGS from the
> > environment so that only the CFLAGS from qemu configure script will be
> > used. This matches what is done in kvm.rpm and qemu.rpm where for
> > example RPM_OPT_FLAGS is not passes as CFLAGS. Otherwise those packages
> > would not build as well.
>
> I think it is a bug to try to invoke the Xen build system with CFLAGS
> set. So I don't think it's a good idea to try to fix it up.
Its a way to pass RPM_OPT_FLAGS to build the tools. This includes things
like fortify-source (whatever the exact spelling is) and other global
flags to build a distro.
What other ways exist to pass that to the buildsystem for the tools?
Olaf
next prev parent reply other threads:[~2012-03-01 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 16:45 [PATCH] tools/qemu-xen: remove CFLAGS for qemu build Olaf Hering
2012-03-01 17:42 ` Ian Jackson
2012-03-01 17:53 ` Olaf Hering [this message]
2012-03-01 18:20 ` Ian Jackson
2012-03-01 19:08 ` Olaf Hering
2012-03-02 11:51 ` Olaf Hering
2012-03-14 12:04 ` Ian Jackson
2012-03-14 16:46 ` Olaf Hering
2012-03-14 18:07 ` Olaf Hering
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=20120301175325.GA8395@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).