xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/configure: add options to pass EXTRA_CLFAGS
Date: Thu, 15 Mar 2012 16:32:34 +0100	[thread overview]
Message-ID: <20120315153234.GC7421@aepfle.de> (raw)
In-Reply-To: <CAPLaKK72SQtNjsg9crpw51o37eaQMAzMXcxVhN34DXMt0_VB_Q@mail.gmail.com>

On Thu, Mar 15, Roger Pau Monné wrote:


> > To make sure the EXTRA_CFLAGS appear first in the command line
> > tools/Rules.mk must include config/Tools.mk before Config.mk.

> > +++ b/tools/Rules.mk
> > @@ -3,8 +3,8 @@
> >  # `all' is the default target
> >  all:
> >
> > +include $(XEN_ROOT)/config/Tools.mk
> >  include $(XEN_ROOT)/Config.mk
> > -include $(XEN_ROOT)/config/Tools.mk
> 
> Do we really need to change the order? User-defined flags should
> appear after necessary tools build flags, if not a user might use some
> flags that break the build without knowing.

This affects the tools build. If the extra flags really should go to the
end, then APPEND_CFLAGS can be reused and the ordering change above can
be removed.

> >  export _INSTALL := $(INSTALL)
> >  INSTALL = $(XEN_ROOT)/tools/cross-install
> > diff -r 6dd1395c07cb -r 994ac398f4dc tools/configure.ac
> > --- a/tools/configure.ac
> > +++ b/tools/configure.ac
> > @@ -55,6 +55,12 @@ AC_ARG_VAR([APPEND_INCLUDES],
> >     [List of include folders to append to CFLAGS (without -I)])
> >  AC_ARG_VAR([APPEND_LIB],
> >     [List of library folders to append to LDFLAGS (without -L)])
> > +AC_ARG_VAR([EXTRA_CFLAGS_XEN_TOOLS],
> > +    [Extra CFLAGS to build tools])
> > +AC_ARG_VAR([EXTRA_CFLAGS_QEMU_TRADITIONAL],
> > +    [Extra CFLAGS to build qemu-traditional])
> > +AC_ARG_VAR([EXTRA_CFLAGS_QEMU_XEN],
> > +    [Extra CFLAGS to build qemu-xen])
> 
> The change looks good to me in terms of configure modifications, but
> I'm not sure of the names, shouldn't qemu-traditional be
> qemu-xen(-traditional) and qemu-xen be qemu-(xen-)upstream?

I cant comment on that.

What I have seen right now is that other external tools may need their
own EXTRA_CFLAGS_xx variable. Like gcc47 is currently unhappy with ipxe
at least.

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-03-15 15:32 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
2012-03-15 14:38 ` Roger Pau Monné
2012-03-15 15:32   ` Olaf Hering [this message]
  -- 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=20120315153234.GC7421@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=roger.pau@entel.upc.edu \
    --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).