From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Purcareata Bogdan-B43198 <B43198@freescale.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: bitbake clean / cleanall / cleansstate not working
Date: Sat, 20 Apr 2013 08:39:57 +0100 [thread overview]
Message-ID: <1366443597.10502.140.camel@ted> (raw)
In-Reply-To: <E7E317BD5B5D764682EEAC13B01676E2650BB2@039-SN2MPN1-021.039d.mgd.msft.net>
On Wed, 2013-04-17 at 09:42 +0000, Purcareata Bogdan-B43198 wrote:
> Hello,
>
> I am using Yocto with BB_VERSION = "1.18.0" and the commands in the subject do not seem to work - they don't do anything. The image has the packages built.
>
> $ bitbake -c cleanall gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded.
>
> $ bitbake -c clean gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and all succeeded.
>
> $ bitbake -c cleansstate gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
>
> The information in [ ... ] is not really relevant. I just wanted to
> give the output message. I know the error description is vague, but so
> is this behavior. I don't know what it could be further related to.
What exactly are you trying to clean? The above messages say it ran 1, 2
or 3 tasks and they all succeeded.
Keep in mind there are several "gcc" components such as gcc-cross,
gcc-cross-initial and so on. "gcc" is the one used on target.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-20 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 9:42 bitbake clean / cleanall / cleansstate not working Purcareata Bogdan-B43198
2013-04-20 7:39 ` Richard Purdie [this message]
2013-04-22 9:42 ` Purcareata Bogdan-B43198
2013-04-22 11:05 ` Paul Eggleton
2013-04-22 14:22 ` Purcareata Bogdan-B43198
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=1366443597.10502.140.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B43198@freescale.com \
--cc=bitbake-devel@lists.openembedded.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.