From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Finding the linux kernel headers version of a gcc cross toolchain
Date: Sat, 18 Apr 2020 22:48:53 +0300 [thread overview]
Message-ID: <87mu78d17e.fsf@tarshish> (raw)
In-Reply-To: <CAPm8-H4pjFOoCq4xX36wA7vRN2utKtxs3G3Gdbf07T29jPgL5g@mail.gmail.com>
Hi L-C,
On Fri, Apr 17 2020, Laurentiu-Cristian Duca wrote:
> Hello buildroot community,
>
> When choosing an external toolchain for Buildroot
> we must specify the kernel headers version used to build the
> corresponding toolchain.
> Can you please tell me how to detect the kernel headers version of the
> external toolchain?
Look for the linux/version.h header file from your toolchain. Use the
LINUX_VERSION_CODE and KERNEL_VERSION macros that this file defines to
find the kernel headers version.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2020-04-18 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 15:08 [Buildroot] Finding the linux kernel headers version of a gcc cross toolchain Laurentiu-Cristian Duca
2020-04-18 19:48 ` 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=87mu78d17e.fsf@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