Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Thu, 5 Jun 2014 20:05:39 +0300	[thread overview]
Message-ID: <20140605170539.GP4193@tarshish> (raw)
In-Reply-To: <CAE9DZUT8+z0NF5O6sh=y4svCfQW0bh1Zt4r7OM9fe9nYvk-O0w@mail.gmail.com>

Hi Dallas,

On Thu, Jun 05, 2014 at 11:34:41AM -0500, Dallas Clement wrote:
> Hi All - I have seen posts on this subject before.  It looks like things
> flamed out.
> 
> http://lists.gnu.org/archive/html/autoconf/2012-11/msg00022.html
> 
> 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
> sitting on their !#@ while autoconf is running.  Most of my packages rely
> on autotools and it seems that most of the time spent is running configure
> scripts.
> 
> Can anyone offer some advice on how to speed things up with autoconf?  Or
> is it a lost cause?

You may try to enable parallel build which is disabled by default. Look for 
'.NOTPARALLEL:' in the top level Makefile. Make sure to read the comment above 
it.

Hope this helps.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-06-05 17:05 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 [this message]
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
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=20140605170539.GP4193@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox