From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: tmp/work-shared and sstate
Date: Tue, 10 Feb 2015 10:28:29 -0700 [thread overview]
Message-ID: <54DA3FBD.2000503@mlbassoc.com> (raw)
If I run a build where the kernel package is brought in via
sstate, tmp/work-shared (in particular the kernel-source tree)
is not populated. This will break at least these recipes:
meta-fsl-arm/recipes-multimedia/gstreamer/gst-fsl-plugin_4.0.2.bb
meta-fsl-arm/recipes-multimedia/alsa/fsl-alsa-plugins_1.0.25.bb
These programs reference the kernel includes directly for some
ARM/i.MX specific headers (e.g. <linux/mxcfb.h>). These headers
are not part of the mainline kernel which is used to create the
kernel headers that populates tmp/sysroots, so the build fails.
Note: I'm not sure of the mechanism that lets these programs
peek into the kernel build (I looked at them but nothing jumped
out), but they do build find if the kernel is actually built
and not just brought in by sstate.
Is this an error & if so, which recipe is at fault? The FSL
recipes, or the new kernel build/classes?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-02-10 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 17:28 Gary Thomas [this message]
2015-02-10 18:13 ` [meta-freescale] tmp/work-shared and sstate Christopher Larson
2015-02-10 18:13 ` Christopher Larson
2015-02-10 18:35 ` [meta-freescale] " Gary Thomas
2015-02-11 11:23 ` Gary Thomas
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=54DA3FBD.2000503@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--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.