All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Don Slutz <dslutz@verizon.com>
Cc: xen-devel@lists.xensource.com,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	qemu-devel@nongnu.org, 1257099@bugs.launchpad.net,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Bug 1257099] [NEW] QEMU fails to build on CentOS 5.10 with relocation R_X86_64_PC32 error
Date: Mon, 09 Dec 2013 14:22:07 +0100	[thread overview]
Message-ID: <52A5C3FF.2030809@redhat.com> (raw)
In-Reply-To: <52A5BBE6.9070000@terremark.com>

Il 09/12/2013 13:47, Don Slutz ha scritto:
> On 12/05/13 22:20, Don Slutz wrote:
>> On 12/05/13 16:24, Richard Henderson wrote:
>>> 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~
> [snip]
> 
> Attached is a much better version.  It drops -fPIE and adds -fPIC for
> libtool.

It's not much better, because using position-independent code for shared
libraries is really platform-dependent knowledge of the kind that
libtool is supposed to hide.

For example, on Mac OS X everything is position-independent by default.
 And on some platforms you have -fpic instead of -fPIC.

So I prefer the patch you had that disabled libtool if the platform is
buggy.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Don Slutz <dslutz@verizon.com>
Cc: xen-devel@lists.xensource.com,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	qemu-devel@nongnu.org, 1257099@bugs.launchpad.net,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Bug 1257099] [NEW] QEMU fails to build on CentOS 5.10 with relocation R_X86_64_PC32 error
Date: Mon, 09 Dec 2013 14:22:07 +0100	[thread overview]
Message-ID: <52A5C3FF.2030809@redhat.com> (raw)
In-Reply-To: <52A5BBE6.9070000@terremark.com>

Il 09/12/2013 13:47, Don Slutz ha scritto:
> On 12/05/13 22:20, Don Slutz wrote:
>> On 12/05/13 16:24, Richard Henderson wrote:
>>> 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~
> [snip]
> 
> Attached is a much better version.  It drops -fPIE and adds -fPIC for
> libtool.

It's not much better, because using position-independent code for shared
libraries is really platform-dependent knowledge of the kind that
libtool is supposed to hide.

For example, on Mac OS X everything is position-independent by default.
 And on some platforms you have -fpic instead of -fPIC.

So I prefer the patch you had that disabled libtool if the platform is
buggy.

Paolo

  reply	other threads:[~2013-12-09 13:23 UTC|newest]

Thread overview: 30+ 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 13:25   ` Stefano Stabellini
2013-12-03 14:06   ` [Qemu-devel] " Paolo Bonzini
2013-12-03 14:06     ` Paolo Bonzini
2013-12-03 20:19     ` [Qemu-devel] " Don Slutz
2013-12-03 20:19       ` Don Slutz
2013-12-03 17:15   ` [Qemu-devel] " Paolo Bonzini
2013-12-03 17:15     ` Paolo Bonzini
2013-12-04  1:32 ` [Qemu-devel] " Don Slutz
2013-12-04  1:32   ` Don Slutz
2013-12-05 15:18   ` Paolo Bonzini
2013-12-05 15:18     ` Paolo Bonzini
2013-12-05 19:09     ` [Qemu-devel] " Don Slutz
2013-12-05 19:09       ` Don Slutz
2013-12-05 21:24     ` [Qemu-devel] " Richard Henderson
2013-12-05 21:24       ` Richard Henderson
2013-12-06  3:20       ` [Qemu-devel] " Don Slutz
2013-12-06  3:20         ` Don Slutz
2013-12-09 12:47         ` [Qemu-devel] " Don Slutz
2013-12-09 12:47           ` Don Slutz
2013-12-09 13:22           ` Paolo Bonzini [this message]
2013-12-09 13:22             ` Paolo Bonzini
2013-12-14 20:21             ` [Qemu-devel] " Don Slutz
2013-12-14 20:21               ` Don Slutz
2013-12-15 16:01               ` [Qemu-devel] " Don Slutz
2013-12-15 16:01                 ` Don Slutz
2013-12-07 13:27     ` [Qemu-devel] " 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=52A5C3FF.2030809@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=1257099@bugs.launchpad.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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 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.