From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected
Date: Mon, 18 Jan 2016 23:24:57 +0100 [thread overview]
Message-ID: <20160118232457.472dc051@free-electrons.com> (raw)
In-Reply-To: <877fj64jhn.fsf@dell.be.48ers.dk>
Peter,
On Mon, 18 Jan 2016 23:21:08 +0100, Peter Korsgaard wrote:
> > I also don't like the way the patch is implemented, but I think the
> > problem raised by this patch is real. Sometimes people have kernel
> > sources that contain some custom kernel headers needed for their
> > userspace libraries/applications, and we have no mechanism to allow
> > them to use their custom kernel source for the linux-headers package,
> > which is a bit annoying.
>
> Yeah, true. It does require that these custom header files are really
> exported (so they get installed by headers_install) which in my
> experience is not always the case.
>
> What I have told people to do in the past instead is to either copy the
> needed definitions into their user space code or add
> -I$(LINUX_DIR)/include (if they build their kernel in Buildroot) like
> E.G. xdriver_xf86-video-imx does it.
Yes, I know there are ways around it.
But it does seem weird to many users that the "linux" package provides
some many possibilities for fetching/patching the kernel, and still the
linux-headers package downloads a completely different kernel version,
with less possibilities of using a custom version.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-18 22:24 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 [this message]
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
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=20160118232457.472dc051@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.