From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] host-pcc: enable building with -m32 or -m64
Date: Fri, 27 May 2011 09:12:15 +0200 [thread overview]
Message-ID: <4DDF4ECF.5060406@redhat.com> (raw)
In-Reply-To: <4DDEA34C.4040304@linux.vnet.ibm.com>
On 05/26/2011 09:00 PM, Stefan Berger wrote:
> With the below patch I can build either ppc (-m32) or ppc64 (-m64)
> versions of Qemu (on a ppc64 host) when passing these compiler flags via
> 'configure ... --extra-cflags="-m32"'.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>
> ---
> configure | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> Index: qemu-git/configure
> ===================================================================
> --- qemu-git.orig/configure
> +++ qemu-git/configure
> @@ -807,7 +807,14 @@ case "$cpu" in
> arm*)
> host_guest_base="yes"
> ;;
> - ppc*)
> + ppc)
> + QEMU_CFLAGS="-m32 $QEMU_CFLAGS"
> + LDFLAGS="-m32 $LDFLAGS"
> + host_guest_base="yes"
> + ;;
> + ppc64)
> + QEMU_CFLAGS="-m64 $QEMU_CFLAGS"
> + LDFLAGS="-m64 $LDFLAGS"
> host_guest_base="yes"
> ;;
> mips*)
The patch doesn't seem to match the description. I would have guessed
that with this patch you _do not_ need to pass these compiler flags via
--extra-cflags anymore.
Also, -m32/-m64 are really CPPFLAGS, not CFLAGS since they affect also
the compiler's include path.
Paolo
prev parent reply other threads:[~2011-05-27 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:00 [Qemu-devel] [PATCH] host-pcc: enable building with -m32 or -m64 Stefan Berger
2011-05-26 19:14 ` malc
2011-05-26 19:27 ` Stefan Berger
2011-05-26 20:20 ` Andreas Färber
2011-05-26 20:31 ` Stefan Berger
2011-05-26 20:42 ` malc
2011-05-26 21:24 ` Andreas Färber
2011-05-26 22:25 ` Stefan Berger
2011-05-29 21:09 ` Andreas Färber
2011-05-29 22:07 ` Stefan Berger
2011-05-27 7:12 ` Paolo Bonzini [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=4DDF4ECF.5060406@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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 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.