termux-packages/packages/teseq/build.sh

TERMUX_PKG_HOMEPAGE=https://www.gnu.org/software/teseq/
TERMUX_PKG_DESCRIPTION="Tool for analyzing control characters and terminal control sequences"
TERMUX_PKG_LICENSE="GPL-3.0"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=1.1.1
TERMUX_PKG_REVISION=1
TERMUX_PKG_SRCURL=https://mirrors.kernel.org/gnu/teseq/teseq-${TERMUX_PKG_VERSION}.tar.xz
TERMUX_PKG_SHA256=230d2b4a587542284c415b33557a27774f5ad1580ed9db272bcd1e2034ea0589
TERMUX_PKG_EXTRA_CONFIGURE_ARGS="teseq_cv_vsnprintf_works=yes"
Use more source checksums 2017-03-27 01:56:11 +02:00			`TERMUX_PKG_HOMEPAGE=https://www.gnu.org/software/teseq/`
Initial push 2015-06-13 01:03:31 +02:00			`TERMUX_PKG_DESCRIPTION="Tool for analyzing control characters and terminal control sequences"`
add licenses for more packages 2019-01-21 13:53:58 +01:00			`TERMUX_PKG_LICENSE="GPL-3.0"`
explicitly set maintainer for each package In issue https://github.com/termux/termux-packages/issues/6160 I have found that community repo "its-pointless.github.io" specifies us as maintainer for its packages. This is NOT TRUE and potentially misleads people using these packages. Now TERMUX_PKG_MAINTAINER will contain a default value which is neutral and not specify maintainer. So all packages now have to override it to the correct value. [skip ci] %ci:no-build 2020-12-20 14:16:34 +01:00			`TERMUX_PKG_MAINTAINER="@termux"`
teseq: Update from 1.1 to 1.1.1 2015-08-16 20:45:08 +02:00			`TERMUX_PKG_VERSION=1.1.1`
Rebuild all packages with control.tar.gz Bump the version of all old packages that contained a control.tar.gz file - as of now only control.tar.xz is used. See #1398. 2017-09-15 00:38:35 +02:00			`TERMUX_PKG_REVISION=1`
Switch from ftp.gnu.org to mirrors.kernel.org 2016-09-25 00:42:39 +02:00			`TERMUX_PKG_SRCURL=https://mirrors.kernel.org/gnu/teseq/teseq-${TERMUX_PKG_VERSION}.tar.xz`
Use more source checksums 2017-03-27 01:56:11 +02:00			`TERMUX_PKG_SHA256=230d2b4a587542284c415b33557a27774f5ad1580ed9db272bcd1e2034ea0589`
Fix rpl_malloc when cross compiling 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. 2015-11-15 22:04:37 +01:00			`TERMUX_PKG_EXTRA_CONFIGURE_ARGS="teseq_cv_vsnprintf_works=yes"`