From c527fd1f14c27855a37f2e8ac5346ce8d940ced2 Mon Sep 17 00:00:00 2001 From: Tudor Florea Date: Thu, 16 Oct 2014 03:05:19 +0200 Subject: initial commit for Enea Linux 4.0-140929 Migrated from the internal git server on the daisy-enea-point-release branch Signed-off-by: Tudor Florea --- meta/recipes-devtools/m4/m4/ac_config_links.patch | 30 +++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 meta/recipes-devtools/m4/m4/ac_config_links.patch (limited to 'meta/recipes-devtools/m4/m4/ac_config_links.patch') diff --git a/meta/recipes-devtools/m4/m4/ac_config_links.patch b/meta/recipes-devtools/m4/m4/ac_config_links.patch new file mode 100644 index 0000000000..275c0b2e7d --- /dev/null +++ b/meta/recipes-devtools/m4/m4/ac_config_links.patch @@ -0,0 +1,30 @@ +Upstream-Status: Inappropriate [configuration] + +This patch fixes a build problem for m4-native experienced on Ubuntu 9.10, +where autoconf/automake (AC_CONFIG_LINKS) ends up making GNUmakefile a +symlink to itself. + +The patch comments out ac_config_links directly in configure, +as autoreconf is not actually run for m4-native. + +I believe it should be safe, as GNUmakefile is actually unpacked from +source, and what we want is to is to not touch it. + +Tested on x86_64_linux (Ubuntu 8.04 and 9.10). + +2009-11-10 Esben Haabendal + +diff -urN m4-1.4.13.orig/configure m4-1.4.13/configure +--- m4-1.4.13.orig/configure 2009-11-10 10:54:00.301707097 +0100 ++++ m4-1.4.13/configure 2009-11-10 10:54:17.314206379 +0100 +@@ -14860,8 +14860,8 @@ + # only, it does not matter if we skip the link with older autoconf. + # Automake 1.10.1 and earlier try to remove GNUmakefile in non-VPATH + # builds, so use a shell variable to bypass this. +- GNUmakefile=GNUmakefile +- ac_config_links="$ac_config_links $GNUmakefile:$GNUmakefile" ++ # GNUmakefile=GNUmakefile ++ # ac_config_links="$ac_config_links $GNUmakefile:$GNUmakefile" + + + -- cgit v1.2.3-54-g00ecf