From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] linux-headers: Allow building a 4.8-rc kernel
Date: Mon, 12 Sep 2016 23:02:05 +0200 [thread overview]
Message-ID: <20160912230205.6f8f9270@free-electrons.com> (raw)
In-Reply-To: <1473696955-24297-1-git-send-email-festevam@gmail.com>
Hello,
On Mon, 12 Sep 2016 13:15:54 -0300, Fabio Estevam wrote:
> diff --git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
> index 7fea748..8601eff 100644
> --- a/package/linux-headers/Config.in.host
> +++ b/package/linux-headers/Config.in.host
> @@ -86,6 +86,10 @@ choice
> bool "Linux 4.7.x kernel headers"
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_7
>
> + config BR2_KERNEL_HEADERS_4_8
> + bool "Linux 4.8-rc kernel headers"
> + select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_8
Adding this is not good if you don't update the
BR2_DEFAULT_KERNEL_HEADERS option. With this change, if an user selects
BR2_KERNEL_HEADERS_4_8, he will get a build error as it will try to
download linux-.tar.bz2.
So I've dropped this chunk. It will be added once 4.8 final is
released, together with the BR2_DEFAULT_KERNEL_HEADERS change.
I've also updated the commit log to be more explanatory.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-12 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 16:15 [Buildroot] [PATCH v2 1/2] linux-headers: Allow building a 4.8-rc kernel Fabio Estevam
2016-09-12 16:15 ` [Buildroot] [PATCH v2 2/2] mx6ulpico: Use kernel 4.8-rc5 Fabio Estevam
2016-09-12 21:02 ` Thomas Petazzoni
2016-09-12 21:02 ` Thomas Petazzoni [this message]
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=20160912230205.6f8f9270@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