From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Fri, 6 Jun 2014 09:15:48 +0200 [thread overview]
Message-ID: <20140606091548.53f07f90@free-electrons.com> (raw)
In-Reply-To: <CAE9DZURmNL1iOcY4UR4CrDkg5DOT46-yy-e1+Ftax1_W0faing@mail.gmail.com>
Dear Dallas Clement,
On Thu, 5 Jun 2014 17:06:48 -0500, Dallas Clement wrote:
> 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.
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?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-06 7:15 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 [this message]
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=20140606091548.53f07f90@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