Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Why must I specify toolchain kernel headers?
Date: Mon, 12 May 2014 07:06:30 +0300	[thread overview]
Message-ID: <20140512040630.GI4096@tarshish> (raw)
In-Reply-To: <CAE21AQp0xD2ZP7pEGCxUZis97vnwN3zLHj=nW-a-Y=bq6rT2Og@mail.gmail.com>

Hi Charles,

On Mon, May 12, 2014 at 01:32:21PM +1200, Charles Manning wrote:
> I don't quite understand why I need to set the kernel header version under
> Toolchain/Kernel headers.
> 
> Surely this can be figured out from the kernel source I am using?
> 
> Setting the version under toolchain/kernel headers makes sense when there
> is no kernel being built, but makes little sense when a kernel is buing
> built.
> 
> Having to set this in multiple places leads to inconsistency.
> 
> ... or have I misunderstood something?

There is a use case for using headers from a newer kernel than the running 
one. Consider, for example, userspace environment that needs to run under 
several kernels of different versions. In this case you generally want to use 
the latest headers for to allow userspace to take advantage of the most recent 
kernel you use. The same userspace programs should also run just fine on older 
kernels, since in most cases userspace fails gracefully when encountering an 
unsupported kernel feature.

You can always set BR2_LINUX_KERNEL_SAME_AS_HEADERS to simplify things for the 
single kernel case, though.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2014-05-12  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  1:32 [Buildroot] Why must I specify toolchain kernel headers? Charles Manning
2014-05-12  4:06 ` Baruch Siach [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=20140512040630.GI4096@tarshish \
    --to=baruch@tkos.co.il \
    --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