qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Dinar Valeev <k0da@opensuse.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Dinar Valeev <dvaleev@suse.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] configure: Enable pie for powerpc and arm Linux
Date: Tue, 05 Nov 2013 18:46:23 +0100	[thread overview]
Message-ID: <52792EEF.5000204@suse.de> (raw)
In-Reply-To: <1383567545-16825-1-git-send-email-dvaleev@suse.com>

Am 04.11.2013 13:19, schrieb Dinar Valeev:
> From: Dinar Valeev <dvaleev@suse.de>
> 
> This patch enables pie for PowerPC and ARM architectures
> 
> Signed-off-by: Dinar Valeev <dvaleev@suse.com>
> ---
>  configure | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/configure b/configure
> index 91372f9..0130e7e 100755
> --- a/configure
> +++ b/configure
> @@ -1297,7 +1297,7 @@ fi
>  
>  if test "$pie" = ""; then
>    case "$cpu-$targetos" in
> -    i386-Linux|x86_64-Linux|x32-Linux|i386-OpenBSD|x86_64-OpenBSD)
> +    i386-Linux|x86_64-Linux|x32-Linux|ppc*-Linux|arm*-Linux|aarch64*-Linux|i386-OpenBSD|x86_64-OpenBSD)
>        ;;
>      *)
>        pie="no"

For the benefit of the list, we have been using the ppc part of this
patch for the openSUSE ppc/ppc64 builds (some helper would otherwise
fail to link), and for our arm/aarch64 builds we've been using
--enable-pie to skip the above test. So those are known to work for us.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2013-11-05 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 12:19 [Qemu-devel] [PATCH] configure: Enable pie for powerpc and arm Linux Dinar Valeev
2013-11-04 20:51 ` Richard Henderson
2013-11-04 21:16   ` Paolo Bonzini
2013-11-05 17:50     ` Andreas Färber
2013-11-05 17:46 ` Andreas Färber [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=52792EEF.5000204@suse.de \
    --to=afaerber@suse.de \
    --cc=dvaleev@suse.com \
    --cc=k0da@opensuse.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).