From: Martin Jansa <martin.jansa@gmail.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: noticeably longer build (link?) times with binutils 2.26
Date: Thu, 11 Feb 2016 20:20:24 +0100 [thread overview]
Message-ID: <20160211192024.GD2595@jama> (raw)
In-Reply-To: <56BCC3F8.9000908@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
On Thu, Feb 11, 2016 at 12:25:12PM -0500, Trevor Woerner wrote:
> On 02/09/16 23:37, Khem Raj wrote:
> > IIRC gold has its own notions to enable gold
> > so you need to enable that
> >
> >> On Feb 9, 2016, at 8:18 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> >>
> >> I've tried every combination I can think of and no matter what I try, if gold is the linker the chromium build always errors out with:
> >>
> >> collect2: fatal error: cannot find 'ld'
>
> Building with gold does cut the build time of the chromium component
> back down.
>
> binutils 2.25, bfd: 00:47:51, 00:44:24, 00:44:25
> binutils 2.26, bfd: 02:07:45, 02:09:31, 02:02:42
>
> binutils 2.26, gold: 00:43:49, 00:45:18, 00:42:51
>
>
> But the only way I could get it to work was to manually perform the
> following steps:
> $ cd <oe tmp dir>/sysroots/<native sysroot>/usr/bin
> $ ln -s <cross toolchain prefix>/<cross toolchain prefix>ld.gold ld.gold
>
> where:
> <native sysroot> = x86_64-linux
> <cross toolchain prefix> = x86_64-poky-linux
>
> to give:
> $ cd <oe-tmp-dir>/sysroots/x86_64-linux
> $ ln -s x86_64-poky-linux/x86_64-poky-linux-ld.gold ld.gold
>
> Maybe I can play with the recipe a bit more to get this to work
> "automatically"; maybe by setting the LD environment variable
> differently or something.
Did you add ld-is-gold to DISTRO_FEATURES?
>
> But, as I said before, the last time I tried booting a gold-linked image
> on the minnow grub2 refused to work :-(
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-02-11 19:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 23:20 noticeably longer build (link?) times with binutils 2.26 Trevor Woerner
2016-02-09 0:25 ` Mark Hatle
2016-02-09 2:56 ` Trevor Woerner
2016-02-09 10:00 ` Burton, Ross
2016-02-09 15:34 ` Trevor Woerner
2016-02-09 2:25 ` Khem Raj
2016-02-09 3:03 ` Trevor Woerner
2016-02-09 3:05 ` Khem Raj
2016-02-10 4:18 ` Trevor Woerner
2016-02-10 4:37 ` Khem Raj
2016-02-11 17:25 ` Trevor Woerner
2016-02-11 17:29 ` Khem Raj
2016-02-11 19:20 ` Martin Jansa [this message]
2016-02-11 22:14 ` Trevor Woerner
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=20160211192024.GD2595@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@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