From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 04/10] toolchain/external: add choice to select 'AT_LEAST_XXX' header version
Date: Mon, 17 Feb 2014 11:44:37 +0100 [thread overview]
Message-ID: <20140217114437.06ee9758@skate> (raw)
In-Reply-To: <CAAXf6LVfv7WWYMykb_FC_BRJxkNxabOJRTPxh-m+vuJSH6rG=w@mail.gmail.com>
Dear Thomas De Schampheleire,
On Mon, 17 Feb 2014 11:32:14 +0100, Thomas De Schampheleire wrote:
> >> Maybe you could also add that if the user is unsure about the exact
> >> version, it's 'safer' to specify an older version than a newer one.
> >> And maybe a way of determining the header version used in a toolchain,
> >> in case the user does not know it.
> >
> > We should simply have a check that ensures the selection is correct.
>
> This was probably answered before, but if we can detect that the
> selection is incorrect, why don't we set the right value
> automatically?
Because we need the values within Kconfig, to show/not show the
different packages. And while we are in Kconfig, we cannot run commands
to test the toolchain that has just been selected by the user. So we
need to ask the user what his toolchain looks like, in order to have
the correct dependencies for packages. And then at build time, we can
check that the configuration selected for the toolchain actually
matches the provided toolchain.
This has already been discussed a million times I guess :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-17 10:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 17:27 [Buildroot] [PATCH 0/10] Add dependency on kernel headers Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 01/10] toolchain/common: add minimum kernel headers options Yann E. MORIN
2014-02-17 22:33 ` Arnout Vandecappelle
2014-02-16 17:27 ` [Buildroot] [PATCH 02/10] manual: document minimal kernel headers dependency Yann E. MORIN
2014-02-16 17:41 ` Samuel Martin
2014-02-16 17:52 ` Yann E. MORIN
2014-02-16 20:03 ` Thomas De Schampheleire
2014-02-16 20:42 ` Yann E. MORIN
2014-02-16 20:45 ` Thomas De Schampheleire
2014-02-16 20:55 ` Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 03/10] package/linux-headers: select appropriate 'AT_LEAST_XXX' header version Yann E. MORIN
2014-02-17 22:41 ` Arnout Vandecappelle
2014-02-20 18:16 ` Yann E. MORIN
2014-02-20 20:17 ` Thomas Petazzoni
2014-02-20 21:06 ` Thomas De Schampheleire
2014-02-20 21:11 ` Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 04/10] toolchain/external: add choice to select " Yann E. MORIN
2014-02-16 20:08 ` Thomas De Schampheleire
2014-02-16 20:47 ` Yann E. MORIN
2014-02-17 8:07 ` Thomas De Schampheleire
2014-02-17 10:30 ` Thomas Petazzoni
2014-02-17 10:32 ` Thomas De Schampheleire
2014-02-17 10:44 ` Thomas Petazzoni [this message]
2014-02-17 18:04 ` Yann E. MORIN
2014-02-17 22:49 ` Thomas Petazzoni
2014-02-17 23:10 ` Arnout Vandecappelle
2014-02-17 18:02 ` Yann E. MORIN
2014-02-17 22:45 ` Arnout Vandecappelle
2014-02-17 23:00 ` Yann E. MORIN
2014-02-17 23:14 ` Arnout Vandecappelle
2014-02-16 17:27 ` [Buildroot] [PATCH 05/10] " Yann E. MORIN
2014-02-17 22:47 ` Arnout Vandecappelle
2014-02-16 17:27 ` [Buildroot] [PATCH 06/10] package/dvb-apps: requires kernel headers >= 3.3 Yann E. MORIN
2014-02-17 22:51 ` Arnout Vandecappelle
2014-02-17 23:24 ` Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 07/10] package/w_scan: requires kernel headers >= 3.0 Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 08/10] package/weston: " Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 09/10] package/tvheadend: requires kernel headers >= 3.2 Yann E. MORIN
2014-02-16 17:27 ` [Buildroot] [PATCH 10/10] package/mmc-utils: requires kernel headers >= 3.0 Yann E. MORIN
2014-02-16 17:36 ` [Buildroot] [PATCH 0/10] Add dependency on kernel headers 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=20140217114437.06ee9758@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