From: Mike Looijmans <mike.looijmans@topic.nl>
To: <yocto@yoctoproject.org>
Subject: Re: Sharing sstate
Date: Fri, 27 Mar 2015 08:46:09 +0100 [thread overview]
Message-ID: <55150AC1.6080202@topic.nl> (raw)
In-Reply-To: <55140D4C.2060107@mlbassoc.com>
On 26-03-15 14:44, Gary Thomas wrote:
> I have two development servers, one running an older version
> of Fedora (x86 *), the other runs a recent Ubuntu (x86_64).
> Both are the same CPU core (Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz)
>
> I've just tried building the same target, using the same version
> of Poky/Yocto, sharing the sstate cache (fully populated) from
> the x86_64 machine with the x86 machine. This was done using
> HTTP. Sadly, there was not a single file found in the cache
> that could be used.
>
> Should this not be expected to work? Does sstate cache only
> work across like systems (32 vs 64 bit hosts)?
The hosts need to be similar for the build tools to be recycled. If they have
different OS versions, or even different CFLAGS you'll see a rebuild of
"native" packages.
It should however be able to recycle things for the target, because these
should not depend on the build host's configuration.
We currently have a "server" with ubuntu 12 on it, while most "clients" run
14. Typically the clients build their own tools, but they do re-use all target
packages (like FPGA bitstream and ARM software packages).
> Also, Mark Hatle mentioned a few days ago that there are ways
> to "lock" versions of the sstate cache. I still haven't found
> any info/documentation on this. Can someone please explain more?
>
> Thanks
>
> (*) I can't update my x86 machine to a more recent (x86_64)
> distribution as I have many older "projects" that only run
> on that hardware and no time/opportunity to upgrade, hence
> my desire to share in this manner.
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2015-03-27 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 13:44 Sharing sstate Gary Thomas
2015-03-26 23:13 ` Gary Thomas
2015-03-27 7:46 ` Mike Looijmans [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-27 14:22 Gary Thomas
2011-09-27 16:17 ` Richard Purdie
2011-09-28 2:25 ` 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=55150AC1.6080202@topic.nl \
--to=mike.looijmans@topic.nl \
--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.