Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Sat, 7 Jun 2014 11:04:32 +0200	[thread overview]
Message-ID: <20140607110432.3e52d064@free-electrons.com> (raw)
In-Reply-To: <CAE9DZURp2teR8p5WP3OQEZyZ71qD=8U97q03cRd0yHbTsz8FwA@mail.gmail.com>

Dear Dallas Clement,

On Fri, 6 Jun 2014 11:14:15 -0500, Dallas Clement wrote:

> Hi Thomas.  Thanks very much for looking at my configuration.  I think you
> certainly nailed it.
> I have a lot of packages, and perl and mysql especially are taking a long
> time.  My build recipes
> for both of these are a year or two out of date.  In fact, my perl recipe
> is still using qemu to build
> instead of perl cross.  Hopefully updating this recipe will help some,
> though as you pointed out
> it is still using MAKE1.

Right. I'll send a separate e-mail to Fran?ois Perrad about this (our
Perl guy), because it seems like other build systems are building Perl
in parallel.

> Yep, very speedy SSDs and 64 GB for RAM.  Because of all the serialization
> in this build process,
> building from a large ram disk seems to make little difference.

Right. So you have a good build configuration, there's not much we can
do here.

> > There is another thing that strikes out in your configuration: there
> > are many packages that we don't have in Buildroot, and that don't seem
> > to be specific to your company or project. What about submitting your
> > new packages upstream?
> 
> Yes, I can certainly do that.  There's a lot here.  Much of it is obscure.
> Please let me know which ones you are most
> interested in.

Could you make a list of the packages that you've added, and that are
open-source? I'm pretty sure a majority of them could potentially be
useful to have in Buildroot.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-06-07  9:04 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
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 [this message]
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=20140607110432.3e52d064@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox