Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: PowerPC / gcc / prelink
Date: Fri, 30 Oct 2015 17:44:28 -0500	[thread overview]
Message-ID: <5633F2CC.6090903@windriver.com> (raw)
In-Reply-To: <CAMKF1sp4Jd5765g2mvDAir6MgO_4pNRvByNV9_MPjrQX-NviEw@mail.gmail.com>

On 10/30/15 4:59 PM, Khem Raj wrote:
> On Fri, Oct 30, 2015 at 2:42 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> I finally chased down the PowerPC prelink problem.  It appears to be within GCC.
>>
>> On most systems GCC (for PPC) is configured with --enable-secureplt.  However,
>> the OE-Core version is not.  The prelinker assumes that for certain types of
>> relocations that the PPC_GOT table will exist, otherwise it gives up.  (It
>> doesn't know how to do the relocations in the old style .bss-got table.)
>>
>> I'm wondering if there is a reason that PPC is defaulting to the old style
>> .bss-got (other then the secureplt was not enabled by default).
>>
>> Is this something we should do in all cases, or should this become a
>> DISTRO_FEATURE like the mips 'mplt' setting?
>>
>>
>> I'm still building systems and running tests, but adding --enable-secureplt to
>> both the gcc-cross-initial, and gcc-cross appear to have resolved the prelinking
>> issues.
> 
> enabling secureplt is ok, ensure that binutils is configured correctly as well.

binutils 2.25.1 has all of the support needed for secure-plt.  So I don't
believe there are any issues there.

I'll prepare a patch that changes the default configuration.

--Mark

> 
>>
>> --Mark



      reply	other threads:[~2015-10-30 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 21:42 PowerPC / gcc / prelink Mark Hatle
2015-10-30 21:59 ` Khem Raj
2015-10-30 22:44   ` Mark Hatle [this message]

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=5633F2CC.6090903@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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