From 10028104ff53ec7b338019e685f43ecd2c4625e0 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 21 Jul 2022 14:47:36 +0100 Subject: autotools: Drop relative configure path workaround Calling configure with a relative path to the build directory was a nice workaround to remove hardcoded paths from files. We have proper prefix remapping code now and these relative paths escape that modern code. Drop the obsolete approach and allow the prefix remapping to handle things. This ensures the contents of debug source directories is correct as the build directory from the tarball name may not match the on target debug directory. Signed-off-by: Richard Purdie --- meta/classes/autotools.bbclass | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass index 4ab2460990..d56d820f66 100644 --- a/meta/classes/autotools.bbclass +++ b/meta/classes/autotools.bbclass @@ -86,9 +86,7 @@ CONFIGURE_SCRIPT ?= "${AUTOTOOLS_SCRIPT_PATH}/configure" AUTOTOOLS_AUXDIR ?= "${AUTOTOOLS_SCRIPT_PATH}" oe_runconf () { - # Use relative path to avoid buildpaths in files - cfgscript_name="`basename ${CONFIGURE_SCRIPT}`" - cfgscript=`python3 -c "import os; print(os.path.relpath(os.path.dirname('${CONFIGURE_SCRIPT}'), '.'))"`/$cfgscript_name + cfgscript=${CONFIGURE_SCRIPT} if [ -x "$cfgscript" ] ; then bbnote "Running $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} $@" if ! CONFIG_SHELL=${CONFIG_SHELL-/bin/bash} ${CACHED_CONFIGUREVARS} $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} "$@"; then -- cgit 1.2.3-korg