[OE-core] [CONSOLIDATED PULL 05/28] autoconf: no need to hardcode the full path to m4

Saul Wold sgw at linux.intel.com
Fri Oct 14 05:33:03 UTC 2011


From: Christopher Larson <kergoth at gmail.com>

This way autom4te uses m4 as it finds it in the PATH, rather than
hardcoding any particular path.

Signed-off-by: Christopher Larson <kergoth at gmail.com>
---
 meta/recipes-devtools/autoconf/autoconf_2.68.bb |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-devtools/autoconf/autoconf_2.68.bb b/meta/recipes-devtools/autoconf/autoconf_2.68.bb
index c6209a3..21b5fb3 100644
--- a/meta/recipes-devtools/autoconf/autoconf_2.68.bb
+++ b/meta/recipes-devtools/autoconf/autoconf_2.68.bb
@@ -1,6 +1,6 @@
 require autoconf.inc
 
-PR = "r2"
+PR = "r3"
 
 PARALLEL_MAKE = ""
 
@@ -27,4 +27,6 @@ RDEPENDS_${PN}_virtclass-native = "m4-native gnu-config-native"
 
 SRC_URI_append_virtclass-native = " file://fix_path_xtra.patch"
 
+EXTRA_OECONF += "ac_cv_path_M4=m4"
+
 BBCLASSEXTEND = "native"
-- 
1.7.6.2





More information about the Openembedded-core mailing list