xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/configure: add options to pass EXTRA_CLFAGS
Date: Thu, 15 Mar 2012 14:46:36 +0100	[thread overview]
Message-ID: <20120315134636.GA31539@aepfle.de> (raw)
In-Reply-To: <4F61FD510200007800078ABF@nat28.tlf.novell.com>

On Thu, Mar 15, Jan Beulich wrote:

> > This patch extends configure to recognize three environment variables
> > which will be written to config/Tools.mk so they will be reused with
> > each make invocation:
> >   EXTRA_CFLAGS_XEN_TOOLS= specifies CFLAGS for the tools build.
> >   EXTRA_CFLAGS_QEMU_TRADITIONAL= specifies CFLAGS for old qemu.
> >   EXTRA_CFLAGS_QEMU_XEN= specifies CFLAGS for new qemu.
> > The new feature can be used like this in a rpm xen.spec file:
> > 
> >    env \
> >    EXTRA_CFLAGS_XEN_TOOLS="${RPM_OPT_FLAGS}" \
> >    EXTRA_CFLAGS_QEMU_TRADITIONAL="${RPM_OPT_FLAGS}" \
> >    EXTRA_CFLAGS_QEMU_XEN="${RPM_OPT_FLAGS}" \
> >    ./configure \
> >    	--libdir=%{_libdir} \
> >    	--prefix=/usr
> >    make
> > 
> > To make sure the EXTRA_CFLAGS appear first in the command line
> 
> Wouldn't one rather want them to appear last (to eventually override
> other settings, namely the optimization level)?

If thats desired then the EXTRA_CFLAGS_XEN_TOOLS part is not needed,
APPEND_CFLAGS= could be used for that purpose. But this variable is not
yet handled as autoconf variable.

Olaf

  reply	other threads:[~2012-03-15 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 13:19 [PATCH] tools/configure: add options to pass EXTRA_CLFAGS Olaf Hering
2012-03-15 13:31 ` Jan Beulich
2012-03-15 13:46   ` Olaf Hering [this message]
2012-03-15 14:38 ` Roger Pau Monné
2012-03-15 15:32   ` Olaf Hering
  -- strict thread matches above, loose matches on Subject: below --
2012-03-27 12:42 Olaf Hering
2012-03-27 13:04 ` Olaf Hering
2012-03-28 18:56 Olaf Hering
2012-04-03 17:13 ` Ian Jackson

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=20120315134636.GA31539@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@suse.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 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).