From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: autotools_preconfigure not removing separate B
Date: Thu, 9 May 2013 12:48:04 +0200 [thread overview]
Message-ID: <20130509104804.GD3188@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Do we really need -e "${CONFIGURESTAMPFILE}" check in autotools_preconfigure?
In some cases when do_configure is failing (but after creating e.g. .qmake.cache)
it would be better to start with clean B on 2nd attempt to configure it, but
CONFIGURESTAMPFILE wasn't created yet.
Does someone remember why we need to test CONFIGURESTAMPFILE existence first
(was it only to prevent cat ${CONFIGURESTAMPFILE} to fail?)
autotools_preconfigure() {
if [ -n "${CONFIGURESTAMPFILE}" -a -e "${CONFIGURESTAMPFILE}" ]; then
if [ "`cat ${CONFIGURESTAMPFILE}`" != "${BB_TASKHASH}" -a "${S}" != "${B}" ]; then
echo "Previously configured separate build directory detected, cleaning ${B}"
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2013-05-09 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 10:48 Martin Jansa [this message]
2013-05-09 20:57 ` autotools_preconfigure not removing separate B Richard Purdie
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=20130509104804.GD3188@jama \
--to=martin.jansa@gmail.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