From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Stuart Weaver <Stuart.Weaver@datapath.co.uk>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: compiling out-of-tree modules with master
Date: Tue, 1 Dec 2015 12:16:23 -0500 [thread overview]
Message-ID: <565DD5E7.8050809@windriver.com> (raw)
In-Reply-To: <2DCC166D4F5C8443941662E1E67FD5C178773046@LEICESTER.internal.datapath.co.uk>
On 15-12-01 11:57 AM, Stuart Weaver wrote:
> Hi All,
>
> I’m currently merging my Yocto repo up to master (from Daisy). I’m
> having problems compiling some of the out-of-tree modules that we have
> which I’ve tracked down to the Makefiles looking for:
>
> include/generated/autoconf.h
>
> include/generated/uapi/linux/version.h
>
> Now I originally had to heavily patch these Makefiles to include
> variables like KERNEL_SRC and KERNEL_VERSION as they were just calling
> shell commands (e.g. echo uname –a). However the KERNEL_SRC is pointing
> to the new location of the source in ‘work-shared’ where none of the
> generated .h files are.
STAGING_KERNEL_BUILDDIR is what you want. That's where all the artifacts
of the build required for external module builds are placed.
Bruce
>
> Could someone inform on the differences in workflow and which variables
> I should be using to point to the build source of the kernel (i.e.
> work/corei7-intel-common-poky-linux/linuux-yocto/3.19.5…./linux-corei7-64-intel-common-standard-build)?
>
> *Best Regards,*
>
> *Stuart*
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
>
prev parent reply other threads:[~2015-12-01 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:57 compiling out-of-tree modules with master Stuart Weaver
2015-12-01 17:16 ` Bruce Ashfield [this message]
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=565DD5E7.8050809@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=Stuart.Weaver@datapath.co.uk \
--cc=yocto@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.