In some cases this will introduce cycles which could likely be cleaned
up by only depending on some unix tools instead of the whole autotools.
Rebuilding doesn't make much sense at this point since it just adds a subset
of base-devel which is still installed by default.
* PKGBUILD:
- add (make)dependency to libiconv (apparently new with m4 1.4.19)
- remove INSTALL directive, since routines in m4.install are
automatically covered by makepkg
** prepare:
- remove any M4 macro patches to make running 'autoreconf' obsolete
- add patches for test suite
** build:
- apply VPATH build
- fool configure that gcc is CYGWIN to be able to use CONFIGURE straight
out of the box (without patching code bits missing MSYS as system).
For GNULIB this is a nightmare.
- enable multi-threading
**check:
- pass list of tests still failing after applying patch skipping tests
due to permission access issues
(see 0003-m4-1.1.19-skip-tests-when-temp-directories-cannot-be-generated.patch)
on to 'make check' via variable XFAIL_TESTS. This applies to GNULIB
tests checking the environment only, but not M4 features, though.
- NB: All tests except those in variable XFAIL_TESTS succeed.
* 0001-m4-1.4.19-tests-refine-error-messages.patch:
- added, no functional change
* 0002-m4-1.1.19-skip-tests-when-temp-directories-cannot-be-generated.patch:
- added, skip test failing in the prep phase when generating directories
with particular access rights
* m4.install:
- removed (since obsolete as functionality covered by pacman/makepkg)
* m4-1.4.18-msys2.patch:
- removed, since configure is used straight out of the box being fooled
that a CYGWIN compiler is used
* upgrade some broken packages
* correct some broken urls/checksums
* use secure urls where possible
* use stable url for ncurses
* some whitespace fixes
Remaining md5sums either didn't download or
didn't pass checksum tests.
