Since 2004 we've been carrying a patch[1] make autoreconf pass --foreign to
automake. Presumably at the time this was due to many upstreams using
hand-coded bootstrap scripts that passed --foreign manually, but we were using
autoreconf. These days many projects have added foreign to AM_INIT_AUTOMAKE and
use autoreconf directly, so this patch isn't as critical as it used to be.
Signed-off-by: Ross Burton <ross.burton@intel.com>
[1] oe-classic
2ab2a92eadaf2f80410d8746099f8a9b1b81ff91
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
+++ /dev/null
-Upstream-Status: Pending
-
---- autoconf-2.59/bin/autoreconf.in~autoreconf-foreign 2004-05-09 20:55:06.000000000 -0400
-+++ autoconf-2.59/bin/autoreconf.in 2004-05-09 20:55:55.000000000 -0400
-@@ -184,6 +184,8 @@
-
- $aclocal_supports_force = `$aclocal --help` =~ /--force/;
-
-+ $automake .= ' --foreign';
-+
- # Dispatch autoreconf's option to the tools.
- # --include;
- $autoconf .= join (' --include=', '', @include);
SRC_URI += "file://autoreconf-include.patch \
file://check-automake-cross-warning.patch \
file://autoreconf-exclude.patch \
- file://autoreconf-foreign.patch \
file://autoreconf-gnuconfigize.patch \
file://config_site.patch \
file://remove-usr-local-lib-from-m4.patch \