diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2019-06-22 11:40:06 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2019-06-22 11:40:06 +0100 |
| commit | 7a86906b67693cc65671d3e1476835d3a7e13092 (patch) | |
| tree | 9de1b9e2cf77833183d4e5ffab2e94d0403ef725 /dev-libs/libgdata | |
| parent | d56d144655e3785864da43c9acb6c228ef9360ae (diff) | |
gentoo resync : 22.06.2019
Diffstat (limited to 'dev-libs/libgdata')
| -rw-r--r-- | dev-libs/libgdata/files/libgdata-0.17.9-ax2019-compat.patch | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/dev-libs/libgdata/files/libgdata-0.17.9-ax2019-compat.patch b/dev-libs/libgdata/files/libgdata-0.17.9-ax2019-compat.patch new file mode 100644 index 000000000000..c73e3f9eaee2 --- /dev/null +++ b/dev-libs/libgdata/files/libgdata-0.17.9-ax2019-compat.patch @@ -0,0 +1,20 @@ +autoconf-archive-2019.01.06 breaks AX_CODE_COVERAGE usage by requiring +a different integration inside Makefile.am. This would be fine if the +local m4/ax_code_coverage.m4 would get used, but eaclocal parses out +the install from ACLOCAL_AMFLAGS, and calls aclocal with that, which +overwrites ax_code_coverage.m4 with the newer version, obviously +breaking the usage of all that in Makefile.am. +Workaround it by patching out the --install argument, thus using the +tarball copy of it (older version), which works with Makefile.am +without further patching. + +--- a/Makefile.am ++++ b/Makefile.am +@@ -1,6 +1,6 @@ + SUBDIRS = . po docs gdata/tests + +-ACLOCAL_AMFLAGS = --install -I m4 ${ACLOCAL_FLAGS} ++ACLOCAL_AMFLAGS = -I m4 ${ACLOCAL_FLAGS} + + DISTCHECK_CONFIGURE_FLAGS = + MAINTAINERCLEANFILES = |