Files
poky/meta/recipes-devtools/m4/m4/ac_config_links.patch
Nitin A Kamble e080d8e18e gcc: remove unused patches and move patches in proper dir
gcc: update upstream-status for patches

python: update upstream-status for patches

libtool: update upstream-status of patches

m4: update upstream status for patches

eglibc: remove unused patches

eglibc: update upstream status of patches

glibc: update upstream-status of patches & remove unused patches

(From OE-Core rev: d10df0e5a363fe8b305ffac7e8ac231da8e07552)

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-18 14:32:47 +01:00

31 lines
1.1 KiB
Diff

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 <eha@doredevelopment.dk>
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"