- Fixes https://github.com/termux/termux-packages/issues/27603
- These `man3` manpages conflicting with the packages `zlib` and `perl` existed in Erlang 26
- But from Erlang 27.0 though Erlang 28.2, these manpages were removed upstream, and Termux `erlang` was not built with manpages until Erlang 27
- But in Erlang 28.3, these manpages reappeared after https://github.com/erlang/otp/pull/10237, so the conflicting manpages must now be removed, while preserving all the non-conflicting manpages
- Fixes https://github.com/termux/termux-packages/issues/24624
- This is able to make the commands `man erl` and `erl -man erl` both work, and also, several others
like `man run_erl`, `erl -man run_erl`, and more. Unfortunately,
it is **not** possible to get the `erl -man io` to fully work, but the erlang command
`h(io).` inside the interactive `erl` shell already provides a help page for `io`,
and also, **both Arch Linux and Debian also cannot currently run the command `erl -man io`**
**successfully, even while all their erlang packages are installed**.
The reason this happened is because Erlang version 27 upstream no
longer supports the `erl -man io` command, so all implementations of
it will be at best stuck at the manpage content from Erlang version
26.
- building docs requires using the hostbuilt `erlang`, and that hostbuilt
`erlang` must be a full build with ssl and termcap enabled to avoid errors
and build all docs matching the featureset of the Android build.
The `Makefile` automatically detects and uses this hostbuilt `erlang`
to build the docs if it was the last `erlang` built.
- Unlike the `-DCMAKE_INSTALL_PREFIX` argument that CMake users might be familiar with,
the `--prefix` argument of autotools `configure` does not seem to typically cause the configure step to
attempt to find and import dependencies in that prefix, only sets the installation destination,
so unlike the configure step of CMake projects, it is safe to use with `$TERMUX_PREFIX` during
`termux_step_host_build()`. This message is written so that this example is not accidentally
used as a reference to attempt a similar technique for any CMake-based package.
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
