From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: BB_NO_NETWORK and own-mirrors not working with meta-systemd
Date: Thu, 20 Sep 2012 14:42:27 +0100 [thread overview]
Message-ID: <4100342.qsm4CZIotx@helios> (raw)
In-Reply-To: <CAMAb8ZN0Yb4km-X0wyUDsbRYYSC53B62F+ZPYRVNEmae7QeVsA@mail.gmail.com>
On Thursday 20 September 2012 09:30:19 Evade Flow wrote:
> I guess I'll try the BFI approach of restarting the build from scratch next.
> `:-o.
We'd really rather people didn't do this as it does not help us to diagnose
and fix problems.
> Incidentally, searching the OpenEmbedded manual for 'cleanslate'
> turns up no hits. Is this some kind of 'secret' command? Where can I learn
> about other such commands?
As Gary pointed out the command is "cleansstate". The OpenEmbedded manual has
not been kept up-to-date I'm afraid - but the good news is there is an up-to-
date and comprehensive set of documentation set provided by the Yocto Project
here:
http://www.yoctoproject.org/documentation
FYI you can do "bitbake -c listtasks <targetname>" which will list all of the
valid tasks, you can remove do_ from the start of these to get commands you
can use with -c.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-20 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:34 BB_NO_NETWORK and own-mirrors not working with meta-systemd Evade Flow
2012-09-19 16:50 ` Gary Thomas
2012-09-19 17:15 ` Evade Flow
2012-09-19 17:23 ` Gary Thomas
2012-09-19 17:33 ` Evade Flow
2012-09-19 22:30 ` Evade Flow
2012-09-20 0:13 ` Gary Thomas
2012-09-20 0:43 ` Khem Raj
2012-09-20 13:30 ` Evade Flow
2012-09-20 13:38 ` Gary Thomas
2012-09-20 13:42 ` Paul Eggleton [this message]
2012-09-20 14:12 ` Evade Flow
2012-09-20 20:08 ` Evade Flow
2012-09-20 20:32 ` William Mills
2012-09-20 22:30 ` Brian Lloyd
2012-09-20 21:41 ` Paul Eggleton
2012-09-20 22:12 ` Evade Flow
2012-09-20 22:20 ` Khem Raj
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=4100342.qsm4CZIotx@helios \
--to=paul.eggleton@linux.intel.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.