From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Possible bug in bitbake
Date: Thu, 13 Sep 2012 14:15:16 -0500 [thread overview]
Message-ID: <505230C4.5090107@windriver.com> (raw)
In-Reply-To: <CAP9ODKpy==dnOV-MtxLck0nLm0juBPiVSNwf=_M3gt12tCqXXQ@mail.gmail.com>
On 9/13/12 1:41 PM, Otavio Salvador wrote:
> Hello,
>
> Rogerio and Daiane, here copied, found a bug in bitbake (we managed to
> reproduce it in denzil). The output in console when it happens can be
> seen at:
>
> https://groups.google.com/d/msg/meta-fsl-arm/7W9bwxqslnk/htEiOcaJMH8J
>
> The way to reproduce it is very easy:
>
> * bitbake gnutls -c cleansstate
> * remove gnutls from download cache
> * bitbake gnutls
>
> Adding gnutls back to download cache make the build succeed.
>
There is a stamp file in the download cache. If you don't clear that, then it
will think it's still there.
bitbake gnutls -c distclean
that should remove from the download cache, the stamp file, and all of the
actions of cleansstate.
--Mark
next prev parent reply other threads:[~2012-09-13 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 18:41 Possible bug in bitbake Otavio Salvador
2012-09-13 19:15 ` Mark Hatle [this message]
2012-09-13 19:23 ` Saul Wold
2012-09-13 23:45 ` 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=505230C4.5090107@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox