this package's configure script checks only for $PKGCONFIG, but that variable
is currently only set globally in $TERMUX_ON_DEVICE_BUILD=false
mode. In $TERMUX_ON_DEVICE_BUILD=true mode, only $PKG_CONFIG is set globally.
ld.lld: error: undefined symbol: libiconv
many packages manually set this universally without comment,
but a pattern can be observed that reverse dependencies of libiconv
seem to always require this in $TERMUX_ON_DEVICE_BUILD=true mode,
and it gets set whenever someone creates $TERMUX_ON_DEVICE_BUILD=true support
for one of them.
see the commit message here:
bab423c2bd
- This is the `$TERMUX_PREFIX/include` portion of #21835
- Replace `-I` with `-isystem` in strategic locations: changes the include order of headers in `$TERMUX_PREFIX/include` relative to headers inside the source code of packages currently being built, so that if any headers inside the source code of the package being built have the exact same file names as headers inside `$TERMUX_PREFIX/include`, the headers from inside the source code of the package will be used, instead of the headers from inside `$TERMUX_PREFIX/include`, which would not be correct.
- Previous discussion was here 3dc455672c (diff-8c775c171f451b21463be103116ad5a4c2d0c54d3fb4ff4b59e987f98fc9c348)
- Prevents many _potential_ `$TERMUX_PREFIX/include`-related errors (that are often only reproducible when reusing a single docker container to compile multiple packages) in the following packages (and possibly other packages):
- `nasm`
- `bitlbee`
- `emacs`
- `gdb`
- `libjxl`
- `libmediainfo`
- `maxcso`
- `nodejs`
- `pipewire`
- `rust`
- `sqlcipher`
- `tome2`
- `weggli`
- `zip`
- `proxmark3`
- `handbrake`
- This include order causes the `$TERMUX_ON_DEVICE_BUILD=false` build codepath to match the behavior of the `clang` binary from the `main/clang` package (i.e. the `$TERMUX_ON_DEVICE_BUILD=true` codepath), which is caused by the `-DDEFAULT_SYSROOT` setting that is built into it:
26a76f7b5d/packages/libllvm/build.sh (L40)
- `simulavr`: the current `simulavr` `build.sh` runs `mv $TERMUX_PREFIX/include ...`, that is not really ideal because it effectively deletes the entire `$TERMUX_PREFIX/include` folder, preventing any other packages that might be built in the same container from using the headers they need from `$TERMUX_PREFIX/include` (and also potentially creating a malformed `simulavr` package `.deb` if any other packages were installed info `$TERMUX_PREFIX` beforehand). This rewrites the `simulavr` package in a way that avoids destroying `$TERMUX_PREFIX/include`.
Some packages have issues with parallel builds and need to set
TERMUX_MAKE_PROCESSES=1. All other build variables that package
recipes set are prefixed with TERMUX_PKG, use that for MAKE_PROCESSES
as well for consistency.
%ci:no-build
Commit af18f1dac0b5 ("scripts: start_build: create libpthread and
librt as well") added helper libs so that packages that try to find
these libs can do so.
%ci:no-build
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
* imagemagick: update to 7.0.10.2
* fossil: update to 2.10
Had to disable tests checking for sqlite3 as they try to run cross-compiled tests
* automake: update to 1.16.2
* ghostscript: update to 9.52
* cmake: update to 3.17.0
* git: update to 2.26.0
* krb5: update to 1.18
* ldc: update to 1.20.1
