From: Paolo Bonzini <pbonzini@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rules.mak: Use -r instead of -Wl, -r to fix building when PIE is default
Date: Mon, 28 Nov 2016 16:38:50 +0100 [thread overview]
Message-ID: <36ee35dd-49ea-f2e3-fa1e-600483b9d4e7@redhat.com> (raw)
In-Reply-To: <20161128152404.sywmey4pdcv7btup@bunk.spdns.de>
On 28/11/2016 16:24, Adrian Bunk wrote:
> On Mon, Nov 28, 2016 at 04:05:33PM +0100, Paolo Bonzini wrote:
>>
>>
>> On 27/11/2016 17:28, Adrian Bunk wrote:
>>> Building qemu fails in distributions where gcc enables PIE
>>> by default (e.g. Debian unstable) with:
>>> /usr/bin/ld: -r and -pie may not be used together
>>>
>>> -r and -pie cannot be used together in the linker,
>>> and position independent is already relocatable.
>>>
>>> Use -r instead of -Wl,-r to avoid gcc passing -r to the
>>> linker when PIE is enabled.
>>>
>>> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>>
>> I think this is a bug in the linker. If the linker is producing
>> relocatable objects by default, it has no reason to refuse -r. Have you
>> tried asking the binutils folks about it too?
>
> The linker knows nothing about this default, gcc is passing -pie
> to the linker.
The linker is receiving "-r -pie". It can satisfy the requirement of
producing a relocatable object by discarding the "-r", but it doesn't.
That'd be a linker bug.
But in fact ELF makes PIE ET_DYN and relocatable ET_REL. That would
make the linker error the right thing, but then I don't understand what
you mean by "position independent is already relocatable".
Paolo
next prev parent reply other threads:[~2016-11-28 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 16:28 [Qemu-devel] [PATCH] rules.mak: Use -r instead of -Wl, -r to fix building when PIE is default Adrian Bunk
2016-11-28 15:05 ` Paolo Bonzini
2016-11-28 15:24 ` Adrian Bunk
2016-11-28 15:38 ` Paolo Bonzini [this message]
2016-11-28 15:42 ` Paolo Bonzini
2016-11-28 19:11 ` Adrian Bunk
2016-11-29 9:33 ` Stefan Hajnoczi
2016-11-29 12:09 ` Paolo Bonzini
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=36ee35dd-49ea-f2e3-fa1e-600483b9d4e7@redhat.com \
--to=pbonzini@redhat.com \
--cc=bunk@stusta.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).