From: "Andreas Färber" <afaerber@suse.de>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xensource.com, Erik Blake <eblake@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] qemu/configure: fix CFLAGS handling for i386
Date: Sat, 31 Mar 2012 17:41:04 +0200	[thread overview]
Message-ID: <4F772590.2000603@suse.de> (raw)
In-Reply-To: <20120330152436.GA31016@aepfle.de>
Hi Olaf,
Am 30.03.2012 17:24, schrieb Olaf Hering:
> 
> configure will generate incorrect CFLAGS which will lead to compile
> errors due to unknown gcc options, IFF CFLAGS was already in the
> environment during configure invocation.
> 
> Add a space before the -march=i486 gcc option.
> 
> This patch is against the qemu-xen tree, but it should apply also to
> qemu.git since it has the same issue. Please apply to both trees.
> 
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
The patch applies fine to upstream QEMU (we should strip leading qemu/
from the commit message though).
This is the only usage of += outside Makefile fragments, so I wonder if
its use may have been by accident. Is it safe in a POSIX context?
Or should we better use CFLAGS="$CFLAGS -march=486"?
For QEMU_CFLAGS we use the pattern QEMU_CFLAGS="-options $QEMU_CFLAGS"
to allow overriding options.
Andreas
> 
> ---
>  configure |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: qemu-xen-dir-remote/configure
> ===================================================================
> --- qemu-xen-dir-remote.orig/configure
> +++ qemu-xen-dir-remote/configure
> @@ -2637,7 +2637,7 @@ int main(int argc, char **argv)
>  }
>  EOF
>    if ! compile_prog "" "" ; then
> -    CFLAGS+="-march=i486"
> +    CFLAGS+=" -march=i486"
>    fi
>  fi
>  
-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply	other threads:[~2012-03-31 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 15:24 [PATCH] qemu/configure: fix CFLAGS handling for i386 Olaf Hering
2012-03-31 15:41 ` Andreas Färber [this message]
2012-03-31 16:46   ` Olaf Hering
2012-04-02  7:54     ` Andreas Färber
2012-03-31 16:52   ` Peter Maydell
2012-03-31 16:55     ` 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=4F772590.2000603@suse.de \
    --to=afaerber@suse.de \
    --cc=eblake@redhat.com \
    --cc=olaf@aepfle.de \
    --cc=qemu-devel@nongnu.org \
    --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).