All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: noticeably longer build (link?) times with binutils 2.26
Date: Tue, 9 Feb 2016 10:34:40 -0500	[thread overview]
Message-ID: <56BA0710.8060207@gmail.com> (raw)
In-Reply-To: <CAJTo0LYQx1cZT=bwmXhJqHtFvujqMNH7qNR=05Ciw_+SCekwKg@mail.gmail.com>

On 02/09/16 05:00, Burton, Ross wrote:
>
> On 9 February 2016 at 02:56, Trevor Woerner <twoerner@gmail.com 
> <mailto:twoerner@gmail.com>> wrote:
>
>     MACHINE          = "qemux86-64"
>
>     Essentially: minnowboard max (turbot, specifically)
>
>
> As an aside, if you're actually building for the MinnowMax then the 
> meta-intel BSP will be a lot better.
>

The images I build for my actual board do use the meta-intel BSP and set 
MACHINE to "intel-corei7-64".

This massive explosion in build time for chromium coincided with me 
adding a new disk to my build machine and moving my Jenkins builds over 
to the new disk. At first I assumed the problem might be related to the 
new disk so I was performing build speed tests on both the old and new 
disks. For this I setup 2 new builds (one on each disk) and set MACHINE 
to qemux86-64 by default and had forgot about it. But you bring up a 
good point, I should be using the same MACHINE (although my Jenkins 
instance is still using the correct MACHINE as is seeing the huge 
increase in build times too).


  reply	other threads:[~2016-02-09 15:34 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 [this message]
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
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=56BA0710.8060207@gmail.com \
    --to=twoerner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.