All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Update gone terribly wrong
Date: Tue, 15 Mar 2011 07:51:34 -0600	[thread overview]
Message-ID: <4D7F6EE6.6070504@mlbassoc.com> (raw)

I updated my Poky tree to current master this morning (4c695dbcd12b295a4215422622006f1f58469297)

Now, when I try to build in an extant tree, I get errors like these:
   /home/local/poky-amltd/scripts/bitbake: line 51: 28850 Segmentation fault      (core dumped) PSEUDO_BINDIR=$PSEUDOBINDIR PSEUDO_LIBDIR=$PSEUDOBINDIR/../lib/pseudo/lib 
PSEUDO_PREFIX=$PSEUDOBINDIR/../../ PSEUDO_DISABLED=1 $PSEUDOBINDIR/pseudo $BITBAKE $@

So, I removed pseudodone and got
   /home/local/poky-amltd/scripts/bitbake: line 43: 28891 Segmentation fault      (core dumped) bitbake pseudo-native tar-replacement-native -c populate_sysroot

So I figured I'd just restart, so I tried this:
   % mv tmp tmp.BAD
   % mv sstate-cache sstate-mirror
   ... set SSTATE_MIRRORS to use the old cache
   %  tail -n3 conf/local.conf
   SSTATE_MIRRORS ?= "\
   file://.* file:///local/p60_poky/sstate-mirror/"

Sadly, it's rebuilding everything, reusing nothing :-(

Any ideas what went wrong and why the sstate mirror is not working (again)?

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


             reply	other threads:[~2011-03-15 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 13:51 Gary Thomas [this message]
2011-03-15 13:58 ` Update gone terribly wrong Gary Thomas
2011-03-15 14:03 ` Richard Purdie
2011-03-15 14:08   ` 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=4D7F6EE6.6070504@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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.