From: Blue Swirl <blauwirbel@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] Add configure option to compile user targets as PIE
Date: Sat, 12 Sep 2009 16:01:49 +0300 [thread overview]
Message-ID: <f43fc5580909120601n1aa2679fn8803c8ecbcea2730@mail.gmail.com> (raw)
In-Reply-To: <cc557aab0909120518j15085ebexd6aa4b4829b78e5f@mail.gmail.com>
On Sat, Sep 12, 2009 at 3:18 PM, Kirill A. Shutemov
<kirill@shutemov.name> wrote:
> On Sat, Sep 12, 2009 at 12:57 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Sat, Sep 12, 2009 at 2:17 AM, Kirill A. Shutemov
>> <kirill@shutemov.name> wrote:
>>> Build uset targers as true PIE if user want to keep qemu
>>> self-virtualizable.
>>
>> With PIE enabled, I get the following error:
>> LINK ppc-linux-user/qemu-ppc
>> /usr/bin/ld: main.o: relocation R_X86_64_TPOFF32 against `thread_env'
>> can not be used when making a shared object; recompile with -fPIC
>> main.o: could not read symbols: Bad value
>> collect2: ld returned 1 exit status
>>
>> Maybe -fPIC should be used as well?
>>
>
> Your binutils(fedora, I guess) is buggy. Please apply this patch or do
> not enable PIE:
> http://git.altlinux.org/people/kas/packages/binutils.git?p=binutils.git;a=blob;f=binutils-2.19.51.0.14-alt-tls-pie.patch
>
Looks like a very recent fix (< 2 months). Can we expect that the
builders already have the fixed version? Maybe the PIE toolchain check
should be restored?
next prev parent reply other threads:[~2009-09-12 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 23:17 [Qemu-devel] [PATCH 1/3] Do not link usermode targets with libhw*.a Kirill A. Shutemov
2009-09-11 23:17 ` [Qemu-devel] [PATCH 2/3] Fix text relocations in linux-user targets Kirill A. Shutemov
2009-09-11 23:17 ` [Qemu-devel] [PATCH 3/3] Add configure option to compile user targets as PIE Kirill A. Shutemov
2009-09-12 9:57 ` Blue Swirl
2009-09-12 12:18 ` Kirill A. Shutemov
2009-09-12 13:01 ` Blue Swirl [this message]
2009-09-12 13:11 ` Kirill A. Shutemov
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=f43fc5580909120601n1aa2679fn8803c8ecbcea2730@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kirill@shutemov.name \
--cc=qemu-devel@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).