summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2017-03-02 12:04:08 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-03-07 20:05:31 +0000
commit2345af9b4829ed3eed5abf60f2483055649f8af7 (patch)
tree96a9a31e4b1957b93c4fe3eb669117d2752caf0d /meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
parentc4901328fe5cf912c0965e5b011b64a95a9bcb9d (diff)
downloadpoky-uninative-1.5.tar.gz
recipes: Move out stale GPLv2 versions to a seperate layeruninative-1.5
These are recipes where the upstream has moved to GPLv3 and these old versions are the last ones under the GPLv2 license. There are several reasons for making this move. There is a different quality of service with these recipes in that they don't get security fixes and upstream no longer care about them, in fact they're actively hostile against people using old versions. The recipes tend to need a different kind of maintenance to work with changes in the wider ecosystem and there needs to be isolation between changes made in the v3 versions and those in the v2 versions. There are probably better ways to handle a "non-GPLv3" system but right now having these in OE-Core makes them look like a first class citizen when I believe they have potential for a variety of undesireable issues. Moving them into a separate layer makes their different needs clearer, it also makes it clear how many of these there are. Some are probably not needed (e.g. mc), I also wonder whether some are useful (e.g. gmp) since most things that use them are GPLv3 only already. Someone could now more clearly see how to streamline the list of recipes here. I'm proposing we mmove to this separate layer for 2.3 with its future maintinership and testing to be determined in 2.4 and beyond. (From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch')
-rw-r--r--meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch77
1 files changed, 0 insertions, 77 deletions
diff --git a/meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch b/meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
deleted file mode 100644
index 98774535d5..0000000000
--- a/meta/recipes-devtools/m4/m4/fix_for_circular_dependency.patch
+++ /dev/null
@@ -1,77 +0,0 @@
1Upstream-Status: Inappropriate [licensing]
2
3The older GPLv2 m4 does not work well with newer autoconf. It causes the
4circular dependency as seen bellow.
5 Removing this m4 file which was needed only forl older autoconf
6
7| configure.ac:34: error: AC_REQUIRE: circular dependency of AC_GNU_SOURCE
8| /build_disk/poky_build/build1/tmp/work/i586-poky-linux/m4-1.4.9-r0/m4-1.4.9/m4/extensions.m4:19: AC_USE_SYSTEM_EXTENSIONS is expanded from...
9| ../../lib/autoconf/specific.m4:310: AC_GNU_SOURCE is expanded from...
10| /build_disk/poky_build/build1/tmp/work/i586-poky-linux/m4-1.4.9-r0/m4-1.4.9/m4/gnulib-comp.m4:21: M4_EARLY is expanded from...
11| configure.ac:34: the top level
12| autom4te: /build_disk/poky_build/build1/tmp/sysroots/x86_64-linux/usr/bin/m4 failed with exit status: 1
13| aclocal: /build_disk/poky_build/build1/tmp/sysroots/x86_64-linux/usr/bin/autom4te failed with exit status: 1
14| autoreconf: aclocal failed with exit status: 1
15
16Nitin A Kamble <nitin.a.kamble@intel.com>
172011/03/16
18
19Index: m4-1.4.9/m4/extensions.m4
20===================================================================
21--- m4-1.4.9.orig/m4/extensions.m4
22+++ m4-1.4.9/m4/extensions.m4
23@@ -6,53 +6,10 @@
24 # gives unlimited permission to copy and/or distribute it,
25 # with or without modifications, as long as this notice is preserved.
26
27-# This definition of AC_USE_SYSTEM_EXTENSIONS is stolen from CVS
28-# Autoconf. Perhaps we can remove this once we can assume Autoconf
29-# 2.61 or later everywhere, but since CVS Autoconf mutates rapidly
30-# enough in this area it's likely we'll need to redefine
31-# AC_USE_SYSTEM_EXTENSIONS for quite some time.
32-
33-# AC_USE_SYSTEM_EXTENSIONS
34-# ------------------------
35-# Enable extensions on systems that normally disable them,
36-# typically due to standards-conformance issues.
37-AC_DEFUN([AC_USE_SYSTEM_EXTENSIONS],
38-[
39- AC_BEFORE([$0], [AC_COMPILE_IFELSE])
40- AC_BEFORE([$0], [AC_RUN_IFELSE])
41-
42- AC_REQUIRE([AC_GNU_SOURCE])
43- AC_REQUIRE([AC_AIX])
44- AC_REQUIRE([AC_MINIX])
45-
46- AH_VERBATIM([__EXTENSIONS__],
47-[/* Enable extensions on Solaris. */
48-#ifndef __EXTENSIONS__
49-# undef __EXTENSIONS__
50-#endif
51-#ifndef _POSIX_PTHREAD_SEMANTICS
52-# undef _POSIX_PTHREAD_SEMANTICS
53-#endif
54-#ifndef _TANDEM_SOURCE
55-# undef _TANDEM_SOURCE
56-#endif])
57- AC_CACHE_CHECK([whether it is safe to define __EXTENSIONS__],
58- [ac_cv_safe_to_define___extensions__],
59- [AC_COMPILE_IFELSE(
60- [AC_LANG_PROGRAM([
61-# define __EXTENSIONS__ 1
62- AC_INCLUDES_DEFAULT])],
63- [ac_cv_safe_to_define___extensions__=yes],
64- [ac_cv_safe_to_define___extensions__=no])])
65- test $ac_cv_safe_to_define___extensions__ = yes &&
66- AC_DEFINE([__EXTENSIONS__])
67- AC_DEFINE([_POSIX_PTHREAD_SEMANTICS])
68- AC_DEFINE([_TANDEM_SOURCE])
69-])
70
71 # gl_USE_SYSTEM_EXTENSIONS
72 # ------------------------
73 # Enable extensions on systems that normally disable them,
74 # typically due to standards-conformance issues.
75 AC_DEFUN([gl_USE_SYSTEM_EXTENSIONS],
76- [AC_REQUIRE([AC_USE_SYSTEM_EXTENSIONS])])
77+ [])