Some mysterious autotools errors are because upstream has a custom
aclocal.m4 that we're deleting it unless we know we're not even running
aclocal. There's a case to be made for removing this deletion logic
on the grounds that aclocal should know what it is doing, but for now
make it clear that we're deleting a file by saying so in the task log.
Signed-off-by: Ross Burton <ross.bur...@arm.com>
---
meta/classes-recipe/autotools.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes-recipe/autotools.bbclass
b/meta/classes-recipe/autotools.bbclass
index a1d8e4b3603..9e89ce40b9e 100644
--- a/meta/classes-recipe/autotools.bbclass
+++ b/meta/classes-recipe/autotools.bbclass
@@ -193,6 +193,7 @@ autotools_do_configure() {
# like it was auto-generated. Work around this by blowing it
away
# by hand, unless the package specifically asked not to run
aclocal.
if ! echo ${EXTRA_AUTORECONF} | grep -q "aclocal"; then
+ bbnote Removing existing aclocal.m4
rm -f aclocal.m4
fi
if [ -e configure.in ]; then
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209571):
https://lists.openembedded.org/g/openembedded-core/message/209571
Mute This Topic: https://lists.openembedded.org/mt/110498404/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
