From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] kernel-headers and external toolchain
Date: Mon, 5 Dec 2011 12:23:42 +0100 [thread overview]
Message-ID: <201112051223.43094.arnout@mind.be> (raw)
Hoi all,
[Please keep me in CC]
I have a configuration with an external toolchain and a custom (git) kernel. This custom kernel exports some custom headers (with extra v4l2 ioctls). However, these don't get copied into staging. Indeed, the kernel-headers target is only included when the internal uClibc toolchain is used.
I have two possible solutions for this.
1. When compiling a kernel, install its headers into staging. This overrides the headers that are included in an external or ct-ng toolchain, which is risky. However, the kernel headers are considered ABI and Linus makes an effort to keep ABI compatibility, so the risk is limited.
2. When compiling the package that relies on these custom headers, add a
-I$(LINUX_DIR)/include to CFLAGS. I feel uncomfortable to rely on the presence of the source directory like that. OTOH, for LINUX_DIR this is anyway unavoidable to compile external modules.
Which solution do the others prefer?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
reply other threads:[~2011-12-05 11:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201112051223.43094.arnout@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