From: Patrick <kpa_info@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Error when adding media-ctl as package
Date: Wed, 09 Jan 2013 10:36:00 +0100 [thread overview]
Message-ID: <50ED3A00.3060907@yahoo.fr> (raw)
In-Reply-To: <20130109095119.39ad1ee9@skate>
On 01/09/2013 09:51 AM, Thomas Petazzoni wrote:
> Dear Patrick,
>
> On Wed, 09 Jan 2013 09:45:12 +0100, Patrick wrote:
>
>> checking linux/media.h usability... no
>> checking linux/media.h presence... no
>> checking for linux/media.h... no
>> ERROR: Kernel header file not found or not usable!
>>
>> I think that a "make headers_install" is missing when compiling the
>> kernel. I use a buildroot external toolchain. How could I say to
>> buildboot to add the "make headers_install" step ?
>
> Normally, the kernel headers are part of the toolchain, so they should
> already be in $(STAGING_DIR)/usr/include without having to do anything
> special.
>
> However, if your toolchain is too old, it may not contain sufficiently
> up-to-date kernel headers. The simplest option is to try to update your
> toolchain to a slightly more recent one, so that media.h is provided
> directly with your toolchain, and we have nothing to do.
>
> If it doesn't work, then it's annoying, because we don't really have a
> good way to install the kernel headers of the kernel being built by
> Buildroot... It's doable, but it would probably mean that the media-ctl
> package would depend on BR2_LINUX_KERNEL, which would make it unusable
> for people who build their kernel outside of Buildroot. Maybe an
> acceptable compromise.
>
> Another solution is to carry a patch in the media-ctl package that adds
> a local copy of the media.h header (and other needed kernel headers).
>
> Thomas
>
Ok I updated to a more recent toolchain and it works.
Thanks for your help
Patrick
next prev parent reply other threads:[~2013-01-09 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 13:27 [Buildroot] Error when adding media-ctl as package Patrick
2013-01-08 20:18 ` Arnout Vandecappelle
2013-01-09 8:06 ` Patrick
2013-01-09 8:27 ` Thomas Petazzoni
2013-01-09 8:45 ` Patrick
2013-01-09 8:51 ` Thomas Petazzoni
2013-01-09 9:36 ` Patrick [this message]
2013-01-09 9:52 ` Thomas Petazzoni
2013-01-09 11:17 ` Patrick
2013-01-09 16:08 ` Patrick
2013-01-09 16:23 ` Thomas Petazzoni
2013-01-09 16:38 ` Patrick
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=50ED3A00.3060907@yahoo.fr \
--to=kpa_info@yahoo.fr \
--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