From: Richard Henderson <rth@twiddle.net>
To: Paolo Bonzini <pbonzini@redhat.com>, Don Slutz <dslutz@verizon.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xensource.com,
1257099@bugs.launchpad.net,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@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: Fri, 06 Dec 2013 10:24:59 +1300 [thread overview]
Message-ID: <52A0EF2B.9000905@twiddle.net> (raw)
In-Reply-To: <52A09933.5090302@redhat.com>
On 12/06/2013 04:18 AM, Paolo Bonzini wrote:
> $ 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
The easy workaround is to drop -fPIE when we're adding -fPIC.
r~
next prev parent reply other threads:[~2013-12-05 21:25 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
2013-12-05 21:24 ` Richard Henderson [this message]
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=52A0EF2B.9000905@twiddle.net \
--to=rth@twiddle.net \
--cc=1257099@bugs.launchpad.net \
--cc=Ian.Campbell@citrix.com \
--cc=dslutz@verizon.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).