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] glibc and --enable-kernel
Date: Thu, 28 Jan 2016 09:36:18 +0100	[thread overview]
Message-ID: <20160128093618.42baf311@free-electrons.com> (raw)
In-Reply-To: <20160128025537.GB5589@tungsten.ozlabs.ibm.com>

Sam,

On Thu, 28 Jan 2016 13:55:37 +1100, Sam Bobroff wrote:

> > Ah, so you're working on PowerPC 64, great! We have a toolchain build
> > problem that I reported on Power PC 64, when building for Power 8:
> > 
> >   http://lists.busybox.net/pipermail/buildroot/2016-January/150338.html
> > 
> > If you have some time to look at it, it would be great.
> 
> No problem, I've replied in that thread :-)

Seen that, thanks!

> Ok that is certainly easier and works for me, so I'll post a patch :-)
> 
> I'm curious tho: when I hacked up some test code I used
> BR2_DEFAULT_KERNEL_HEADERS (which seems to have the same value) but I must
> confess I don't understand the implications of choosing between
> BR2_DEFAULT_KERNEL_HEADERS or BR2_TOOLCHAIN_HEADERS_AT_LEAST. Could you explain
> the difference so I don't have to read so much Make code? ;-)

There would be no real difference between the two for your use case.

BR2_DEFAULT_KERNEL_HEADERS is a string that contains the version number
of the Linux kernel sources chosen in the linux-headers package. It
would contain things like 3.2.76, 4.3.4, etc. or a user-specified
kernel version. It would have worked all fine for your case.

BR2_TOOLCHAIN_HEADERS_AT_LEAST is a string that exists for both the
internal and external toolchains, and which indicates the "series" of
the kernel headers (i.e just 3.2, 3.4, 4.0, etc.).

The only reason that may encourage you to use
BR2_TOOLCHAIN_HEADERS_AT_LEAST instead of BR2_DEFAULT_KERNEL_HEADERS is
an upcoming patch from Yann E. Morin (already submitted but not merged
yet), which allows to tell Buildroot to use the kernel version
specified in the "Kernel" menu as the version for the kernel headers.
In this case, I believe BR2_DEFAULT_KERNEL_HEADERS will not be correct,
while BR2_TOOLCHAIN_HEADERS_AT_LEAST will be.

Best regards,

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

  reply	other threads:[~2016-01-28  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  4:21 [Buildroot] glibc and --enable-kernel Sam Bobroff
2016-01-27  8:21 ` Thomas Petazzoni
2016-01-28  2:55   ` Sam Bobroff
2016-01-28  8:36     ` Thomas Petazzoni [this message]
2016-01-28 23:35       ` Arnout Vandecappelle
2016-02-02 13:27         ` Peter Korsgaard
2016-02-02 16:56 ` Mike Frysinger
2016-02-04  4:10   ` Sam Bobroff

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=20160128093618.42baf311@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