From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Correct way continue build after error
Date: Wed, 13 Jan 2010 16:25:50 +0100 [thread overview]
Message-ID: <hikolt$aul$1@ger.gmane.org> (raw)
In-Reply-To: <4B4DE2A2.2030800@zafena.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13-01-10 16:11, Xerxes Rånby wrote:
> Perepelica Alexander wrote:
>> Hello!
>> I look in docs but didn't find answer for subj. Problem is if build is
>> failed then I change receipt or configs and then what must I do to
>> continue?
>> If I must recompile last stage (with configuring and/or unpacking) are
>> some ways to do that?
> Hi, if you have changed the .bb recipe for the package named "foo" to
> fix the error, then recompile the package from scratch using:
>
> bitbake -c clean foo
> bitbake foo
or just add:
INHERIT += "failure-cleanup"
to your local.conf.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLTeX+MkyGM64RGpERAhDtAJ9H83zpQHxD6A2ARfwBoY7mUsfsTgCcC4PG
i19vKTXNxwhvnJOyOa1gMWo=
=/s3L
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-01-13 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 7:10 Correct way continue build after error Perepelica Alexander
2010-01-13 15:11 ` Xerxes Rånby
2010-01-13 15:25 ` Koen Kooi [this message]
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='hikolt$aul$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-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.