qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Don Slutz <dslutz@verizon.com>
Cc: 1257099@bugs.launchpad.net,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Bug 1257099] [NEW] QEMU fails to build on CentOS 5.10 with relocation R_X86_64_PC32 error
Date: Thu, 5 Dec 2013 14:09:42 -0500	[thread overview]
Message-ID: <52A0CF76.7060706@terremark.com> (raw)
In-Reply-To: <52A09933.5090302@redhat.com>

On 12/05/13 10:18, Paolo Bonzini wrote:
> Il 04/12/2013 02:32, Don Slutz ha scritto:
>> Any hints or pointers about the bug in RHEL5 binutils?  I can try and
>> make a patch to auto detect this.
> Actually it's RHEL5 GCC:
>
> $ cat f.c
> void *
> f(unsigned char *buf, int len)
> {
>      return (void*)0L;
> }
>
>
> void *
> g(unsigned char *buf, int len)
> {
>      return f(buf, len);
> }
> $ gcc -shared -o f.so f.c -fPIE -fPIC
> /usr/bin/ld: /tmp/ccQc9els.o: relocation R_X86_64_PC32 against `f' can not be used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: ld returned 1 exit status
>
>
> The bug is simply that "-fPIE -fPIC" counts as -fPIE rather than -fPIC:
>
> $ gcc -S -o - f.c -fPIE |grep call
> 	call	f                      # PC32 relocation
> $ gcc -S -o - f.c -fPIC |grep call
> 	call	f@PLT                  # PLT32 relocation
>
> On RHEL5:
> $ gcc -S -o - f.c -fPIE -fPIC |grep call
> 	call	f
>
> On RHEL6:
> $ gcc -S -o - f.c -fPIE -fPIC |grep call
> 	call	f@PLT
>
> Paolo
How about this as a patch:

 From 282fba086186ff3b8e2b2b15e647df2b58d082dd Mon Sep 17 00:00:00 2001
From: Don Slutz <dslutz@verizon.com>
Date: Thu, 5 Dec 2013 18:50:18 +0000
Subject: [PATCH] configure: Auto disabling of PIE due to broken toolchain
  support (bug #1257099)

See https://bugs.launchpad.net/bugs/1257099

On RHEL5 GCC, you can get 'relocation R_X86_64_PC32' errors from ld.
So disable PIE is this is true.

Signed-off-by: Don Slutz <dslutz@verizon.com>
---
  configure | 43 +++++++++++++++++++++++++++++++++++--------
  1 file changed, 35 insertions(+), 8 deletions(-)

diff --git a/configure b/configure
index cf8123b..a51a9dd 100755
--- a/configure
+++ b/configure
@@ -1339,23 +1339,50 @@ if test "$pie" != "no" ; then
  #  define THREAD
  #endif

+void *f(unsigned char *buf, int len);
+void *g(unsigned char *buf, int len);
+
+void *
+f(unsigned char *buf, int len)
+{
+    return (void*)0L;
+}
+
+
+void *
+g(unsigned char *buf, int len)
+{
+    return f(buf, len);
+}
+
+#ifdef PIE
  static THREAD int tls_var;

  int main(void) { return tls_var; }
+#endif

  EOF
-  if compile_prog "-fPIE -DPIE" "-pie"; then
-    QEMU_CFLAGS="-fPIE -DPIE $QEMU_CFLAGS"
-    LDFLAGS="-pie $LDFLAGS"
-    pie="yes"
-    if compile_prog "" "-Wl,-z,relro -Wl,-z,now" ; then
-      LDFLAGS="-Wl,-z,relro -Wl,-z,now $LDFLAGS"
+  if compile_prog "-shared -fPIE -fPIC" ""; then
+    if compile_prog "-fPIE -DPIE" "-pie"; then
+      QEMU_CFLAGS="-fPIE -DPIE $QEMU_CFLAGS"
+      LDFLAGS="-pie $LDFLAGS"
+      pie="yes"
+      if compile_prog "" "-Wl,-z,relro -Wl,-z,now" ; then
+        LDFLAGS="-Wl,-z,relro -Wl,-z,now $LDFLAGS"
+      fi
+    else
+      if test "$pie" = "yes"; then
+        error_exit "PIE not available due to missing toolchain support"
+      else
+        echo "Disabling PIE due to missing toolchain support"
+        pie="no"
+      fi
      fi
    else
      if test "$pie" = "yes"; then
-      error_exit "PIE not available due to missing toolchain support"
+      error_exit "PIE not available due to broken toolchain support"
      else
-      echo "Disabling PIE due to missing toolchain support"
+      echo "Disabling PIE due to broken toolchain support"
        pie="no"
      fi
    fi
-- 
1.8.2.1

  reply	other threads:[~2013-12-05 19:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 22:36 [Qemu-devel] [Bug 1257099] [NEW] QEMU fails to build on CentOS 5.10 with relocation R_X86_64_PC32 error Don Slutz
2013-12-03 13:25 ` Stefano Stabellini
2013-12-03 14:06   ` Paolo Bonzini
2013-12-03 20:19     ` Don Slutz
2013-12-03 17:15   ` Paolo Bonzini
2013-12-04  1:32 ` Don Slutz
2013-12-05 15:18   ` Paolo Bonzini
2013-12-05 19:09     ` Don Slutz [this message]
2013-12-05 21:24     ` Richard Henderson
2013-12-06  3:20       ` Don Slutz
2013-12-09 12:47         ` Don Slutz
2013-12-09 13:22           ` Paolo Bonzini
2013-12-14 20:21             ` Don Slutz
2013-12-15 16:01               ` Don Slutz
2013-12-07 13:27     ` Don Slutz
2016-09-28 14:56 ` [Qemu-devel] [Bug 1257099] " T. Huth

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=52A0CF76.7060706@terremark.com \
    --to=dslutz@verizon.com \
    --cc=1257099@bugs.launchpad.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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).