sergiotarxz
/
termux-packages
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
termux-packages/packages/teseq/build.sh

6 lines
319 B
Bash
Raw Normal View History

Initial push
2015-06-13 01:03:31 +02:00
TERMUX_PKG_HOMEPAGE=http://www.gnu.org/software/teseq/
TERMUX_PKG_DESCRIPTION="Tool for analyzing control characters and terminal control sequences"
teseq: Update from 1.1 to 1.1.1
2015-08-16 20:45:08 +02:00
TERMUX_PKG_VERSION=1.1.1
Initial push
2015-06-13 01:03:31 +02:00
TERMUX_PKG_SRCURL=http://ftp.gnu.org/gnu/teseq/teseq-${TERMUX_PKG_VERSION}.tar.xz
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"