From: Alexander Graf <agraf@suse.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc-linux-user: Fix missing symbols in .rel/.rela.plt sections
Date: Tue, 10 Jan 2012 00:11:33 +0100 [thread overview]
Message-ID: <CC4F03C9-C97C-4BF4-AAFB-CEDA5AFD8BA6@suse.de> (raw)
In-Reply-To: <20120109230632.GB711@hall.aurel32.net>
On 10.01.2012, at 00:06, Aurelien Jarno wrote:
> On Mon, Jan 09, 2012 at 02:31:15PM +0100, Alexander Graf wrote:
>>
>> On 07.01.2012, at 21:16, Aurelien Jarno wrote:
>>
>>> Fix .rel.plt sections in the output to not only include .rel.plt
>>> sections from the input but also the .rel.iplt sections and to define
>>> the hidden symbols __rel_iplt_start and __rel_iplt_end around
>>> .rel.iplt as otherwise we get undefined references to these when
>>> linking statically to a multiarch enabled libc (using STT_GNU_IFUNC).
>>
>> Please see:
>>
>> http://patchwork.ozlabs.org/patch/130932/
>>
>> I'd still say that we should fix the linker scripts regardless. Also for 1.0.
>
> I agree that we should either remove them or fix them. Not fixing them
> because they should not be there, but at the same time not removing
> them is a bad idea.
>
> On my side I have also tested that it can work with PROVIDE instead of
> PROVIDE_HIDDEN, so we end-up with the same patches. Now how should we
> proceed to merge that to master, which is the first step before getting
> that into stable?
Either apply yours and rebase mine on top, so ppc64 is fixed too, or apply mine :). I'm rather indifferent on that one.
Alex
next prev parent reply other threads:[~2012-01-09 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 20:16 [Qemu-devel] [PATCH] ppc-linux-user: Fix missing symbols in .rel/.rela.plt sections Aurelien Jarno
2012-01-09 13:31 ` Alexander Graf
2012-01-09 23:06 ` Aurelien Jarno
2012-01-09 23:11 ` Alexander Graf [this message]
2012-01-10 17:29 ` Aurelien Jarno
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=CC4F03C9-C97C-4BF4-AAFB-CEDA5AFD8BA6@suse.de \
--to=agraf@suse.de \
--cc=aurelien@aurel32.net \
--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).