All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ankit Rastogi <Ankit.Rastogi@kpit.com>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: How to export kernel specific headers to userspace
Date: Tue, 19 Jun 2018 14:22:15 +0100	[thread overview]
Message-ID: <0179fbbfddf7680e309b02422761c7478125d1ad.camel@linuxfoundation.org> (raw)
In-Reply-To: <BM1PR0101MB12833B9EE6843CFD07689D6A91700@BM1PR0101MB1283.INDPRD01.PROD.OUTLOOK.COM>

On Tue, 2018-06-19 at 05:16 +0000, Ankit Rastogi wrote:
> Can someone provide any pointers on how to export kernel specific
> headers to userspace?
> 
> I am getting below error while building our one of the component
> which requires kernel uapi headers.
> 
> Error Received:
>  /hdmi-capture/main.c:16:10: fatal error: linux/hdmi_info.h: No such
> file or directory
> > |  #include <linux/hdmi_info.h>
> > |           ^~~~~~~~~~~~~~~~~~~
> > | compilation terminated.
> 
> In yocto 2.5, userspace is boot strapped with linux-libc-headers
> package which uses a set of uapi headers from Linux kernel 4.15. Can
> someone suggest for custom kernels, how to expose uapi headers to
> userspace? Thus create a separate linux-apl-headers package with
> those files.

linux-libc-headers is really there to bootstrap the libc and toolchain,
not provide non-standard kernel headers to userspace. You likely need
to create your own recipe which installs the correct extra headers and
then have your code DEPEND on that recipe.

Cheers,

Richard


  parent reply	other threads:[~2018-06-19 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  5:16 How to export kernel specific headers to userspace Ankit Rastogi
2018-06-19  5:19 ` Ankit Rastogi
2018-06-19  6:50   ` Khem Raj
2018-06-19 13:22 ` Richard Purdie [this message]
2018-06-19 13:56   ` Bruce Ashfield
2018-06-19 13:44 ` Bas Mevissen
2018-06-19 13:55   ` Bruce Ashfield
2018-06-19 14:06     ` Bas Mevissen

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=0179fbbfddf7680e309b02422761c7478125d1ad.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ankit.Rastogi@kpit.com \
    --cc=poky@yoctoproject.org \
    /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.