From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-architecture@lists.openembedded.org,
Phil Blundell <pb@pbcl.net>,
openembedded-devel@lists.openembedded.org
Subject: Re: [Openembedded-architecture] [meta-browser] Chromium and gold linker
Date: Mon, 10 Jul 2017 18:22:27 -0400 [thread overview]
Message-ID: <20170710222227.GF26405@denix.org> (raw)
In-Reply-To: <77972c4b-87e4-6369-5b20-6490a929f149@gmail.com>
On Mon, Jul 10, 2017 at 03:16:54PM -0700, Khem Raj wrote:
>
>
> On 7/10/17 3:07 PM, Denys Dmytriyenko wrote:
> > On Mon, Jul 10, 2017 at 10:35:26PM +0100, Phil Blundell wrote:
> >> On Mon, 2017-07-10 at 17:09 -0400, Denys Dmytriyenko wrote:
> >>> On Mon, Jul 10, 2017 at 02:00:35PM -0700, Khem Raj wrote:
> >>>> On 7/10/17 1:47 PM, Denys Dmytriyenko wrote:
> >>>>> On Mon, Jul 10, 2017 at 04:36:42PM -0400, Denys Dmytriyenko
> >>>>> wrote:
> >>>>>> Khem, et al,
> >>>>>>
> >>>>>> I couldn't find below patch being discussed on this mailing
> >>>>>> list before it got
> >>>>>> merged:
> >>>>>>
> >>>>>> https://github.com/OSSystems/meta-browser/commit/62e323848f569c
> >>>>>> 4cdea5567b1917ce006d7705af
> >>>>>
> >>>>> https://github.com/OSSystems/meta-browser/commit/55a74501bc65c90c
> >>>>> 86e3236b51ec2dc2fc0145fb
> >>>>>
> >>>>> "ld-is-gold just means that my default linker is gold, however we
> >>>>> build
> >>>>> both linkers, so one should be able to enable gold just for
> >>>>> linking
> >>>>> chromium even if default ld is bfd linker."
> >>>>>
> >>>>> I strongly disagree with such interpretation - this would mean
> >>>>> there's NO way
> >>>>> to disable gold linker completely, e.g. for when external
> >>>>> toolchain doesn't
> >>>>> support it.
> >>>
> >>> Copying OE architecture list for further discussion of "ld-is-gold"
> >>> meaning.
> >>
> >> The attribution above is a bit confusing so I'm not quite sure who
> >> wrote what. But it is certainly true that "ld-is-gold" in
> >> DISTRO_FEATURES means, and always has meant, simply that gold is to be
> >> installed as the default linker. In other words, if you invoke plain
> >> "ld", you will get gold, and if you need the BFD linker - usually
> >> because you are using linker scripts that gold doesn't understand -
> >> then you must invoke ld.bfd. See
> >> 207a9013670560d62c793a66f01e19f4760a71a8 from some six years ago for
> >> the place that it was originally added.
> >>
> >> As far as I know, we do not have (and never have had) any
> >> DISTRO_FEATURE that will inhibit gold from being installed altogether,
> >
> > It is not about being installed, but about being supported by the toolchain
> > in use - think of external toolchains not built by OE-Core... The original
> > question was whether it's appropriate to force gold linker in recipes, if
> > ld-is-gold is not set by the distro.
>
> We do not have a set API for external toolchains, and thats also wy
> external toolchains have to contantly adjust with newer OE release.
> however, in this case external toolchains could provide ld.gold that
> symlinks to bfd linker
That is true, yes. Which also reminds me to submit a report to Linaro about
this gold linker breakage...
> >> nor can I immediately think of a reason why this would be generally
> >> useful. Obviously, any DISTRO that wants to do this is welcome to
> >> provide a bbappend for binutils.
> >>
> >> p.
> >>
>
prev parent reply other threads:[~2017-07-10 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:36 [meta-browser] Chromium and gold linker Denys Dmytriyenko
2017-07-10 20:47 ` Denys Dmytriyenko
2017-07-10 21:00 ` Khem Raj
2017-07-10 21:09 ` Denys Dmytriyenko
2017-07-10 21:25 ` Khem Raj
[not found] ` <1499722526.27415.1.camel@pbcl.net>
2017-07-10 22:07 ` [Openembedded-architecture] " Denys Dmytriyenko
2017-07-10 22:16 ` Khem Raj
2017-07-10 22:22 ` Denys Dmytriyenko [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=20170710222227.GF26405@denix.org \
--to=denis@denix.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=pb@pbcl.net \
--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