All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dallas Clement <dallas.a.clement@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Thu, 5 Jun 2014 17:06:48 -0500	[thread overview]
Message-ID: <CAE9DZURmNL1iOcY4UR4CrDkg5DOT46-yy-e1+Ftax1_W0faing@mail.gmail.com> (raw)
In-Reply-To: <20140605224222.0184a9b7@free-electrons.com>

On Thu, Jun 5, 2014 at 3:42 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Dallas Clement,
>
> On Thu, 5 Jun 2014 11:34:41 -0500, Dallas Clement wrote:
>
> > I'm getting killed by autoconf.  My builds take 1.5 hours even with
> ccache
> > turned on.  Most of the cores in my very impressive build machine are
>
> Could you post the build-time.log file of your build, and the .config
> file you're using? What are the specifications of your build machine?
> Do you build inside a virtual machine ? Do you build over NFS ?
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>

You bet.  Please see attached.  I'm in the process of fully upgrading over
to latest buildroot / master from 2012.08 so there is probably still some
deprecated stuff in my .config.

My build machine is a HP server with 8 core Intel(R) Xeon(R) CPU E5-2637 v2
@ 3.50GHz.  The OS is RHEL 6.4 64 bit.  No virtual machine and no NFS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140605/84cb13bb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 47018 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140605/84cb13bb/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build-time.log
Type: application/octet-stream
Size: 119578 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140605/84cb13bb/attachment-0003.obj>

  reply	other threads:[~2014-06-05 22:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 16:34 [Buildroot] autoconf caching Dallas Clement
2014-06-05 17:05 ` Baruch Siach
2014-06-05 17:34 ` Yann E. MORIN
2014-06-05 17:39   ` Dallas Clement
2014-06-05 18:57     ` Yann E. MORIN
2014-06-05 20:42 ` Thomas Petazzoni
2014-06-05 22:06   ` Dallas Clement [this message]
2014-06-06  6:13     ` Thomas Petazzoni
2014-06-06  7:15     ` Thomas Petazzoni
2014-06-06 16:14       ` Dallas Clement
2014-06-06 16:31         ` Mike Zick
2014-06-06 16:45           ` Dallas Clement
2014-06-10  9:32             ` Fabio Porcedda
2014-06-11 17:41               ` Dallas Clement
2014-06-13  9:23                 ` Fabio Porcedda
2014-06-14  0:52                   ` Dallas Clement
2014-06-14  7:57                     ` Thomas Petazzoni
2014-06-18 12:37                     ` Fabio Porcedda
2014-06-07  9:04         ` Thomas Petazzoni
2014-06-08  8:19           ` [Buildroot] [UNSURE]Re: " François Perrad
2014-06-09 20:10             ` Dallas Clement
2014-06-10  7:25             ` Thomas Petazzoni
2014-06-06  5:20 ` [Buildroot] " Waldemar Brodkorb

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=CAE9DZURmNL1iOcY4UR4CrDkg5DOT46-yy-e1+Ftax1_W0faing@mail.gmail.com \
    --to=dallas.a.clement@gmail.com \
    --cc=buildroot@busybox.net \
    /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.