* [Buildroot] Why must I specify toolchain kernel headers?
@ 2014-05-12 1:32 Charles Manning
2014-05-12 4:06 ` Baruch Siach
0 siblings, 1 reply; 2+ messages in thread
From: Charles Manning @ 2014-05-12 1:32 UTC (permalink / raw)
To: buildroot
Hi Build-rooters
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?
Thanks
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140512/4876518d/attachment.html>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] Why must I specify toolchain kernel headers?
2014-05-12 1:32 [Buildroot] Why must I specify toolchain kernel headers? Charles Manning
@ 2014-05-12 4:06 ` Baruch Siach
0 siblings, 0 replies; 2+ messages in thread
From: Baruch Siach @ 2014-05-12 4:06 UTC (permalink / raw)
To: buildroot
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 -
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-05-12 4:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-12 1:32 [Buildroot] Why must I specify toolchain kernel headers? Charles Manning
2014-05-12 4:06 ` Baruch Siach
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox