From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08
Date: Sun, 26 Jan 2014 07:37:46 +0100 [thread overview]
Message-ID: <20140126073746.17723e9c@skate> (raw)
In-Reply-To: <52D4E04B.7020700@mind.be>
Dear Arnout Vandecappelle,
On Tue, 14 Jan 2014 07:59:23 +0100, Arnout Vandecappelle wrote:
> > I really don't know what is best to do. I think I'll do the above and
> > try to get the patch upstreamed. Let's see what hey think about it.
>
> What should definitely be upstreamable, is to add a cache variable for
> this option. Then we can set the cache variable from buildroot like we do
> for so many other things already.
Yes, that is usually the right solution for this type of problem. It
allows to tell configure that we know what we're doing :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-26 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08 Thomas Petazzoni
2014-01-09 19:14 ` Yann E. MORIN
2014-01-09 19:15 ` [Buildroot] [PATCH] package/ola: fix build against google.protobuf Yann E. MORIN
2014-01-09 21:05 ` Peter Korsgaard
2014-01-09 23:29 ` [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08 Thomas Petazzoni
2014-01-11 23:17 ` Yann E. MORIN
2014-01-14 6:59 ` Arnout Vandecappelle
2014-01-14 20:35 ` Yann E. MORIN
2014-01-26 6:37 ` Thomas Petazzoni [this message]
2014-01-26 10:30 ` Yann E. MORIN
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=20140126073746.17723e9c@skate \
--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