All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: Re: Strange sstate problem
Date: Fri, 12 Jun 2015 19:19:51 +0300	[thread overview]
Message-ID: <557B06A7.6070300@reliableembeddedsystems.com> (raw)
In-Reply-To: <557896F3.2040207@mlbassoc.com>

Hi,

On 06/10/2015 10:58 PM, Gary Thomas wrote:
> I'm building for two similar targets and sharing sstate between
> them.  Actually, I build for target A and use that sstate cache
> in my SSTATE_MIRRORS for target B.

If I understand correctly what should happen, then SSTATE_MIRRORS should
point to some build machine, which populates SSTATE and other machines
pull from it.

something like:

SSTATE_MIRRORS ?= "file:///nfs/mount/sstate/PATH"

where PATH will be substituted.

So it looks like you do the right thing.

Is the sequence you do the following?

1) Build for target A (which is the SSTATE_MIRROR for target B)
2) After the build finished you build for target B using the shared
sstate from target A

> 
> If I try to build target B from scratch, i.e. wipe out most
> everything from my build tree:
>   % mv cache sstate-cache tmp old2; rm -fr old&
> I also have a PR server for each target - in local.conf:
>   PRSERV_HOST = "localhost:0"

I think that if you use a shared sstate whoever populates the sstate
should also use a central pr server.

something like:

bitbake-prserv --host <server_ip> --port <port> --start on one machine
and instead of localhost:0 the <server_ip>:<port>

In your case it should not matter, since only target A populates the
shared sstate, but you can give it a try.


> 
> When I build in target B, I'm getting a ton of QA errors, basically
> one for every package selected, e.g.
>   ERROR: QA Issue: Package version for package fsl-alsa-plugins went
> backwards which would break package feeds from (0:1.0.25-r0.2 to
> 0:1.0.25-r0.0) [version-going-backwards]
> 
> What could be going on here?
> 
> n.b. I'm using a fairly recent Poky/Yocto master
> (a05663bfa10352fd5af6ca9a9d7b323c1c099f35)
> 

Regards,

Robert

..."Software is getting slower more rapidly than hardware becomes
faster." - Niklaus Wirth, who attributed it to Martin Reiser.

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2015-06-12 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 19:58 Strange sstate problem Gary Thomas
2015-06-12 16:19 ` Robert Berger [this message]
2015-06-14 20:31 ` Gary Thomas
2015-06-16 13:55   ` Paul Eggleton

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=557B06A7.6070300@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.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.