From: Nikolay Dimitrov <picmaster@mail.bg>
To: Gary Thomas <gary@mlbassoc.com>, Yocto Project <yocto@yoctoproject.org>
Subject: Re: sstate black hole?
Date: Mon, 15 Jun 2015 16:58:55 +0300 [thread overview]
Message-ID: <557EDA1F.7010207@mail.bg> (raw)
In-Reply-To: <557ED498.50406@mlbassoc.com>
Hi Gary,
On 06/15/2015 04:35 PM, Gary Thomas wrote:
> I'm working with i.MX6 targets (meta-fsl-arm*). For these
> targets, some packages are "special" in that they use i.MX6
> specific graphics support. This ends up with an additional
> layer of stratification, so my tmp/work tree has:
> all-amltd-linux
> cortexa9hf-vfp-neon-amltd-linux-gnueabi
> cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi
> teton_p0382-amltd-linux-gnueabi
> x86_64-amltd-linux-gnueabi
> x86_64-linux
>
> The packages that are built in tmp/work/cortex* are architecture
> specific, not target specific, hence my question:
>
> If I build for two i.MX6 targets, identical in every way
> except for the ${MACHINE} name, if I use sstate to share
> the builds from target A when building for target B, why
> are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi
> not shared by sstate? I can see that they are present in
> the sstate cache, but they are always rebuilt for target B.
> I consider this incorrect behaviour as these are the same
> architecture and so they should be sharable via sstate.
>
> Am I missing something here? How can I determine why the
> package from target A (sstate cache) is not usable by target B?
Are these packages (the ones that are getting rebuilt) depending on
machine-specific headers (kernel)?
Regards,
Nikolay
next prev parent reply other threads:[~2015-06-15 13:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 13:35 sstate black hole? Gary Thomas
2015-06-15 13:58 ` Nikolay Dimitrov [this message]
2015-06-15 14:21 ` Martin Jansa
2015-06-15 17:41 ` Gary Thomas
2015-06-15 17:46 ` Martin Jansa
2015-06-15 19:33 ` Gary Thomas
2015-06-16 0:19 ` Gary Thomas
2015-06-16 8:37 ` Paul Eggleton
2015-06-16 10:47 ` Gary Thomas
2015-06-16 12:36 ` Paul Eggleton
2015-06-16 13:21 ` Gary Thomas
2015-06-16 13:46 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2015-04-07 14:52 Gary Thomas
2015-04-07 15:27 ` Christopher Larson
2015-04-07 15:52 ` Gary Thomas
2015-04-07 16:19 ` Martin Jansa
2015-04-07 16:29 ` Gary Thomas
2015-04-07 16:33 ` Martin Jansa
2015-04-07 16:42 ` 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=557EDA1F.7010207@mail.bg \
--to=picmaster@mail.bg \
--cc=gary@mlbassoc.com \
--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.