Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: noticeably longer build (link?) times with binutils 2.26
Date: Mon, 8 Feb 2016 22:03:06 -0500	[thread overview]
Message-ID: <56B956EA.9000404@gmail.com> (raw)
In-Reply-To: <CAMKF1soeyQwt+jDkiLWxgh+7BqnbABHa7f=iFyEmZf8O-BBBYw@mail.gmail.com>

On 02/08/16 21:25, Khem Raj wrote:
> On Mon, Feb 8, 2016 at 3:20 PM, Trevor Woerner <twoerner@gmail.com> wrote:
>> This is more of a "FYI", but I've noticed that the build time of my chromium
>> recipe has gone from ~45 minutes to ~2h15m when the only thing that changes
>> is to move openembedded-core from the commit just before upgrading binutils
>> to version 2.26 ([fd75637] native.bbclass: Set CXXFLAGS from BUILD_CXXFLAGS
>> not BUILD_CFLAGS) to the one immediately after ([86ade2c] binutils: Upgrade
>> to 2.26).
> Is it using gold linker ? if not can you try both bfd and gold

A week or so ago, as part of something else (but before the binutils 
update to 2.26), I tried performing a clean build using the gold linker. 
Unfortunately that image was not able to boot:

https://lists.yoctoproject.org/pipermail/meta-intel/2016-January/003697.html
(but there were no replies)

It dies somewhere between the EFI bootloader and grub2 (or perhaps just 
after grub starts). There's no grub output.

I'll try doing the build with the gold linker, but the results of that 
build might not be useful to me.


  reply	other threads:[~2016-02-09  3:03 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 [this message]
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
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=56B956EA.9000404@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.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