* aapt: use https for homepage
* alpine: use https for homepage
* autossh: use https for homepage
* colordiff: use https for homepage
* dialog: use https for homepage
* exiv2: use https for homepage
* ncurses: use https for homepage
* openal-soft: use https for homepage
* sshpass: use https for homepage
* vttest: use https for homepage
* vttest: use versioned URL
* wol: use https for homepage
* timewarrior: update homepage URL
* dart: update to 2.3.0
* nim: update to 0.19.6
* exiv2: update to 0.27.1
* imagemagick: update to 7.0.8.45
* ncdc: update to 1.22
* ca-certificates: update to 20190515
* cabextract: use https for homepage
* axel: update to 2.17.2
* bat: update to 0.11.0
* mktorrent: update homepage URL
* hugo: update to 0.55.6
* file: update to 5.37
* cmake: update to 3.14.4
* stunnel: update to 5.54
* redis: update to 5.0.5
* libuv: update to 1.29.0
* gmic: update to 2.6.3
* libgnutls: update to 3.6.7.1
Work around rpl_malloc being used, see
http://wiki.buici.com/xwiki/bin/view/Programing+C+and+C%2B%2B/Autoconf+and+RPL_MALLOC
for more information:
"The AC_FUNC_MALLOC macro makes sure that the malloc function when passed a zero
argument returns a valid memory block instead of a NULL pointer. This behaviour
conforms to the GNU C library. Normally, this is a reasonable test that autoconf
makes at build-time. In the case of cross-compilation, however, autoconf cannot
execute a program to verify proper behavior. It makes the conservative assumption
that the target library will produce non-conforming code.
Failure of this test causes autconf to replace malloc() calls with rpl_malloc()
calls. At link time, if there is no rpl_malloc() function, the linker will fail
with an error describing the missing symbol. The autoconf documentation recommends
adding this harmless code to the application to implement the function."
In Termux the rpl_malloc() usage is useless at best, and may also prevent building
some packages as well as giving runtime crashes for libgc-using packages or others
expecting to intercept malloc.
Previously some packages specified worked around this themselves, but the configure
arguments are now moved into build-package.sh.