All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Sharing sstate
Date: Thu, 26 Mar 2015 07:44:44 -0600	[thread overview]
Message-ID: <55140D4C.2060107@mlbassoc.com> (raw)

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)?

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.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2015-03-26 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 13:44 Gary Thomas [this message]
2015-03-26 23:13 ` Sharing sstate Gary Thomas
2015-03-27  7:46 ` Mike Looijmans
  -- 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=55140D4C.2060107@mlbassoc.com \
    --to=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.