Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected
Date: Mon, 18 Jan 2016 18:42:00 +0100	[thread overview]
Message-ID: <569D23E8.7070207@mind.be> (raw)
In-Reply-To: <20160109172908.GA3444@free.fr>

On 09-01-16 18:29, Yann E. MORIN wrote:
> Karoly, All,
> 
> Reviving this old one that is still pending in Patchwork...
> 
> On 2015-03-01 18:17 +0100, Karoly Kasza spake thusly:
>> This change makes it possible to use exactly the same sources for both
>> headers during toolchain building and for kernel building itself, even
>> if custom kernel is selected.
>>
>> That way users can be sure that ABI mismatch won't happen between toolchain
>> and kernel.
> 
> So, I'll try to summarise what we have for now:
> 
>   - select kernel headers version and select kernel version (separately)
> 
>   - select kernel headers version, also used as kernel version.
> 
> What you want to add with this patch is:
> 
>   - select kernel version, also used as kernel headers version.

 Actually, I think the main purpose of this patch is to take the same source for
kernel-headers as you use when building the kernel. This is particularly
important if your kernel is some wild branch that adds extra userspace stuff
(typically, ioctl definitions, but it could also be struct definitions). Failing
this, you have to pass a reference to LINUX_DIR to the build of the package that
uses these symbols.

 That said, it's been years since I ran into such a braindead package that
required specific custom kernel headers. Except for some wicked Broadcom stuff,
of course, but that probably doesn't even build with our linux.mk rules.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2016-01-18 17:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 17:17 [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected Karoly Kasza
2015-03-04 22:37 ` Thomas Petazzoni
2015-03-12 14:07   ` Алексей Бродкин
2016-01-09 17:29 ` Yann E. MORIN
2016-01-18  9:21   ` Peter Korsgaard
2016-01-18 21:47     ` Yann E. MORIN
2016-01-18 21:50       ` Peter Korsgaard
2016-01-18 22:03       ` Thomas Petazzoni
2016-01-18 22:13         ` Yann E. MORIN
2016-01-18 22:21           ` Thomas Petazzoni
2016-01-18 22:21         ` Peter Korsgaard
2016-01-18 22:24           ` Thomas Petazzoni
2016-01-19  8:21             ` Peter Korsgaard
2016-01-19 10:18               ` Thomas Petazzoni
2016-01-19 10:29                 ` Peter Korsgaard
2016-01-19 10:31                   ` Thomas Petazzoni
2016-01-19 10:37                     ` Peter Korsgaard
2016-01-19 17:22                       ` Yann E. MORIN
2016-01-18 17:42   ` Arnout Vandecappelle [this message]
2016-01-19  7:25     ` Алексей Бродкин
2016-01-19 20:10 ` 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=569D23E8.7070207@mind.be \
    --to=arnout@mind.be \
    --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