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] [PATCH] defconfigs: add the _AT_LEAST_X_Y headers options
Date: Sat, 8 Mar 2014 09:42:11 +0100	[thread overview]
Message-ID: <20140308094211.3473be41@skate> (raw)
In-Reply-To: <1394234706-10155-1-git-send-email-yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sat,  8 Mar 2014 00:25:06 +0100, Yann E. MORIN wrote:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> Since commit 2a5cf5e (check kernel headers version), we also need to
> specify the series of the custom kernel headers version.
> 
> The defconfigs file that define such a custom kernel headers version
> now fail to build.
> 
> Add the required _AT_LEAST_X_Y options to those config files. Done with
> this (convoluted but very fast, uch faster ythan manual editing!) rule:
> 
>     for f in $( git grep -l BR2_DEFAULT_KERNEL_VERSION=\"3 ); do
>         grep -E '^BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_' "${f}" >/dev/null && continue
>         sed -r -e '/^(BR2_DEFAULT_KERNEL_VERSION="3\.([[:digit:]]+).*")$/s//\1\nBR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_\2=y/' "${f}"
>     done
> 
> Only kernels >= 3.0 need those options in the defconfig, since the
> default for 2.6.x kernels is correct (selects _AT_LEAST_2_6), and
> the default is not saved in a defconfig.

Applied, thanks.

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

      reply	other threads:[~2014-03-08  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 23:25 [Buildroot] [PATCH] defconfigs: add the _AT_LEAST_X_Y headers options Yann E. MORIN
2014-03-08  8:42 ` 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=20140308094211.3473be41@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