From: Chen Qi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 1/1] autotools: do more cleanup when in do_configure
Date: Mon, 10 Sep 2018 18:02:21 +0800 [thread overview]
Message-ID: <d5a1d1701202d4323e15cb31c7f9a3afca88a00f.1536573689.git.Qi.Chen@windriver.com> (raw)
In-Reply-To: <cover.1536573689.git.Qi.Chen@windriver.com>
I met the following error when compiling some projects.
| configure: error: `LDFLAGS' has changed since the previous run:
| configure: former value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed'
| configure: current value: `-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong -Wl,-z,relro,-z,now'
[snip]
| configure: error: changes in the environment can compromise the build
| configure: error: run `make distclean' and/or `rm .././config.cache' and start over
I think when some recipe inherits autotools-brokensep, it should try to
do more cleanups before configure. So also do 'make distclean' and remove
config.cache just as what the error message told us.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/classes/autotools.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass
index 8768a6a..f577461 100644
--- a/meta/classes/autotools.bbclass
+++ b/meta/classes/autotools.bbclass
@@ -113,6 +113,8 @@ autotools_preconfigure() {
cd ${S}
if [ "${CLEANBROKEN}" != "1" -a \( -e Makefile -o -e makefile -o -e GNUmakefile \) ]; then
oe_runmake clean
+ oe_runmake distclean
+ rm -f ${B}/config.cache
fi
find ${S} -ignore_readdir_race -name \*.la -delete
fi
--
1.9.1
next prev parent reply other threads:[~2018-09-10 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 10:02 [PATCH 0/1] autotools: do more cleanup when in do_configure Chen Qi
2018-09-10 10:02 ` Chen Qi [this message]
2018-09-10 10:24 ` [PATCH 1/1] " Burton, Ross
2018-09-11 1:30 ` ChenQi
2018-09-11 8:08 ` 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=d5a1d1701202d4323e15cb31c7f9a3afca88a00f.1536573689.git.Qi.Chen@windriver.com \
--to=qi.chen@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 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.