From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Re: Possible bug in bitbake
Date: Thu, 13 Sep 2012 12:23:18 -0700 [thread overview]
Message-ID: <505232A6.6040806@linux.intel.com> (raw)
In-Reply-To: <505230C4.5090107@windriver.com>
On 09/13/2012 12:15 PM, Mark Hatle wrote:
> 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
>
I think you mean cleanall!
I don't think we have distclean.
Sau!
> that should remove from the download cache, the stamp file, and all of
> the actions of cleansstate.
>
> --Mark
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-09-13 19:35 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
2012-09-13 19:23 ` Saul Wold [this message]
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=505232A6.6040806@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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