From: Ross Burton Date: Wed, 8 Jan 2025 15:46:35 +0000 (+0000) Subject: autotools: log when we're removing aclocal.m4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d6efd938af8a8260ae464edf4388afea73293ec7;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git autotools: log when we're removing aclocal.m4 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 Signed-off-by: Richard Purdie --- 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