Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] libunwind: Do not use gold for linking
Date: Mon, 8 Aug 2016 18:48:43 -0700	[thread overview]
Message-ID: <FFE62A6A-2AB5-4F99-BD19-0BD85BB048A2@gmail.com> (raw)
In-Reply-To: <CAJTo0LYGGyd20Whnox1TCcrROVx24YybiGWkVaS+JX4U+hxiiQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]


> On Aug 8, 2016, at 4:25 PM, Burton, Ross <ross.burton@intel.com> wrote:
> 
> 
> On 8 August 2016 at 23:51, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote:
> This effectively reverts the commit
> 3dd233ac0c80393824100c54bb525236f8290fd2
> 
> gold now emits errors on copy relocs against
> protected symbols what ld.bfd did in past, however
> it seems its too conservative.
> 
> This does not fix the case for folks who
> use gold as default linker, however it
> does make bintuls 2.27 work with default
> configuration of OE
> 
> Presumably this is blocked by the binutils upgrade and should be merged with it and not beforehand?

Thats right.

> 
> Ross


[-- Attachment #1.2: Type: text/html, Size: 1810 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-08-09  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 22:51 [PATCH 1/2] webkitgtk: Disable gold for mips/mips64 Khem Raj
2016-08-08 22:51 ` [PATCH 2/2] libunwind: Do not use gold for linking Khem Raj
2016-08-08 23:25   ` Burton, Ross
2016-08-09  1:48     ` Khem Raj [this message]
2016-08-09  8:29 ` [PATCH 1/2] webkitgtk: Disable gold for mips/mips64 André Draszik
2016-08-09  8:53   ` Khem Raj

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=FFE62A6A-2AB5-4F99-BD19-0BD85BB048A2@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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