From: ydroneaud@opteya.com (Yann Droneaud)
To: kernelnewbies@lists.kernelnewbies.org
Subject: make headers_install for out-of-tree modules
Date: Wed, 07 Oct 2015 17:09:37 +0200 [thread overview]
Message-ID: <1444230577.3188.73.camel@opteya.com> (raw)
In-Reply-To: <CAF3SDA7+2z5Z_qjkWXAvtWQaCV-hOCXdxfM9BCzN3bbUHTT8Og@mail.gmail.com>
Hi,
Le mercredi 07 octobre 2015 ? 10:51 -0300, Daniel. a ?crit :
> Uhh, as I see from docs, this isn't supported,
>
> --- 2.3 Targets
>
> When building an external module, only a subset of the "make"
> targets are available.
> > From https://www.kernel.org/doc/Documentation/kbuild/modules.txt
>
> So, how can I export ioctl calls defined by an out-of-tree module?
>
I had the same expectation and it was a sad day when I found myself
having to do it manually in the out of tree makefile, having to handle
__user annotations in particular, as it wasn't possible to call
scripts/headers_install.sh as scripts/unifdef.c wasn't compiled and
available in the various kernel build environment provided by
distribution packages.
PS: please, don't top post reply, thanks.
> 2015-10-07 10:46 GMT-03:00 Daniel. <danielhilst@gmail.com>:
> > Hi all,
> >
> > I'm trying to install headers from out-of-tree module. I've writed
> > this[1] Makefile. I have Kbuild files with header-y tokens poiting
> > for
> > propper folders and files. When I run "make headers_install" I got
> > this[2] error message,
> >
> > [1] http://pastebin.com/9f3kYT8k
> > [2] http://pastebin.com/yfi69nUi
> >
> > Any idea?
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2015-10-07 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 13:46 make headers_install for out-of-tree modules Daniel.
2015-10-07 13:51 ` Daniel.
2015-10-07 15:09 ` Yann Droneaud [this message]
2015-10-07 16:09 ` Greg KH
2015-10-08 20:48 ` Daniel.
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=1444230577.3188.73.camel@opteya.com \
--to=ydroneaud@opteya.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).