termux/termux-packages

Some packages cannot be built 3: Revenge of the Xiph

Open

#23,492 opened on Feb 25, 2025

View on GitHub
 (24 comments) (3 reactions) (0 assignees)Shell (4,089 forks)batch import
WIPhas build issueshelp wantedinformationpackagingtracker

Repository metrics

Stars
 (16,216 stars)
PR merge metrics
 (Avg merge 3d 5h) (153 merged PRs in 30d)

Description

  • The last full rebuild run is about 6 months old, and with the recent merger of #22994 now seems like to good time to refresh it, so here we go again.

[!IMPORTANT] Build validation should be done without use of the "fast build" -i/-I flags! https://github.com/termux/termux-packages/blob/4bf2156bd66929740b38bf03cca1b8ed0120e1c8/build-package.sh#L425-L426 e.g.

./scripts/run-docker.sh ./build-package.sh -f [package [, ...]]

We want to verify that every package can be "bootstrapped" without the need for pre-compiled dependencies.

Results of building all packages as of December 3rd, 2025

Package With -I No -I Building all Comment
aapt 🟥 🟥 🟥
ada 🟩 🟩 🟥
alacritty 🟥 🟥 🟥
android-tools 🟥 🟥 🟥
ardour 🟩 🟥 🟥
arpack-ng 🟥 🟥 🟥
asymptote 🟩 🟩 🟥
aterm 🟩 🟥 🟥
atomvm 🟩 🟩 🟥
atril 🟩 🟥 🟥
aubio 🟥 🟥 🟥
audacity 🟩 🟥 🟥
avrdude 🟩 🟩 🟥
bitcoin 🟩 🟩 🟥
cadaver 🟩 🟩 🟥
carbonyl 🟥 🟥 🟥
carbonyl-host-tools 🟩 🟩 🟥
cavif-rs 🟥 🟥 🟥
chromium 🟩 🟥 🟥
chromium-host-tools 🟩 🟩 🟥
cinnamon 🟩 🟥 🟥
clamav 🟥 🟥 🟥
clvk 🟩 🟩 🟥
code-oss 🟥 🟥 🟥
codeblocks 🟩 🟥 🟥
codelldb 🟩 🟥 🟥
cookcli 🟩 🟥 🟥
dvdauthor 🟩 🟩 🟥
electron-for-code-oss 🟩 🟩 🟥
electron-host-tools-for-code-oss 🟩 🟩 🟥
emacs 🟩 🟩 🟥
emacs-x 🟩 🟩 🟥
epiphany 🟩 🟥 🟥
exhale 🟥 🟥 🟥
falkon 🟩 🟩 🟥
fcp 🟥 🟥 🟥
fdroidcl 🟩 🟥 🟥
fio 🟩 🟩 🟥
flameshot 🟩 🟩 🟥
flang 🟩 🟩 🟥
freerdp 🟩 🟩 🟥
gatling 🟥 🟥 🟥
gcal 🟩 🟩 🟥
gforth 🟩 🟩 🟥
glslviewer 🟩 🟩 🟥
gnucash 🟩 🟥 🟥
godot 🟩 🟩 🟥
groonga 🟩 🟥 🟥
gw 🟩 🟩 🟥
heimer 🟩 🟩 🟥
hledger-ui 🟩 🟩 🟥
hugin 🟩 🟥 🟥
ices 🟩 🟩 🟥
inkscape 🟩 🟥 🟥
iptables 🟩 🟩 🟥
iwyu 🟩 🟩 🟥
kbd 🟩 🟩 🟥
kf6-kbookmarks 🟩 🟥 🟥
kf6-kfilemetadata 🟩 🟥 🟥
komorebi 🟩 🟥 🟥
kpipewire 🟩 🟩 🟥
labwc 🟩 🟩 🟥
ldc 🟥 🟥 🟥
lenmus 🟩 🟥 🟥
lgogdownloader 🟩 🟩 🟥
libarrow-cpp 🟩 🟥 🟥
libduckdb 🟩 🟩 🟥
libgtop 🟩 🟩 🟥
libhtmlcxx 🟩 🟩 🟥
libmatekbd 🟩 🟥 🟥
libmateweather 🟩 🟩 🟥
libowfat 🟥 🟥 🟥
librocksdb 🟩 🟩 🟥
libtd 🟩 🟩 🟥
libtvision 🟥 🟥 🟥
libva 🟩 🟩 🟥
libxklavier 🟩 🟥 🟥
libxmlrpc 🟩 🟩 🟥
libxres 🟥 🟥 🟥
llama-cpp 🟩 🟩 🟥
lnd 🟩 🟩 🟥
lr 🟥 🟥 🟥
lua-language-server 🟥 🟥 🟥
lux-cli 🟩 🟩 🟥
lxrandr 🟩 🟥 🟥
manim 🟩 🟥 🟥
marco 🟩 🟥 🟥
mate-applet-brisk-menu 🟩 🟥 🟥
mate-panel 🟩 🟥 🟥
mindforger 🟩 🟥 🟥
mogan 🟥 🟥 🟥
moria 🟥 🟥 🟥
mu 🟩 🟥 🟥
muffin 🟩 🟩 🟥
musescore 🟩 🟩 🟥
mutter 🟩 🟥 🟥
ngspice 🟥 🟥 🟥
notcurses 🟥 🟥 🟥
octave 🟥 🟥 🟥
octave-x 🟥 🟥 🟥
open-zwave 🟥 🟥 🟥
opencv 🟩 🟩 🟥
openethereum 🟥 🟥 🟥
openimageio 🟩 🟩 🟥
openscad 🟩 🟩 🟥
openvdb 🟩 🟩 🟥
pgroonga 🟩 🟥 🟥
pika 🟥 🟥 🟥
polybar 🟩 🟩 🟥
pypy3 🟩 🟩 🟥
python-llvmlite 🟥 🟥 🟥
python-msgpack 🟩 🟩 🟥
python-opencv-python 🟩 🟩 🟥
python-pynvim 🟩 🟩 🟥
python-pyqtwebengine 🟩 🟥 🟥
python-scipy 🟥 🟥 🟥
python-tflite-runtime 🟩 🟩 🟥
qemu-system-x86-64 🟩 🟥 🟥
qrupdate-ng 🟥 🟥 🟥
qt-creator 🟩 🟥 🟥
qt5-qtwebengine 🟥 🟥 🟥
qt6-qtwebengine 🟩 🟩 🟥
rq 🟥 🟥 🟥
rsnapshot 🟩 🟩 🟥
rtmpdump 🟩 🟩 🟥
rtorrent 🟥 🟥 🟥
sbcl 🟩 🟩 🟥
smalltalk 🟩 🟩 🟥
solidity 🟩 🟩 🟥
spectacle 🟩 🟥 🟥
spek 🟩 🟥 🟥
sshfs 🟥 🟥 🟥
suitesparse 🟥 🟥 🟥
sundials 🟩 🟥 🟥
supercollider 🟩 🟩 🟥
surf 🟩 🟥 🟥
sway 🟩 🟩 🟥
swi-prolog 🟩 🟩 🟥
swift 🟥 🟥 🟥
sysprop 🟩 🟥 🟥
tasksh 🟩 🟥 🟥
taskwarrior 🟥 🟥 🟥
tcc 🟥 🟥 🟥
telegram-bot-api 🟩 🟩 🟥
telegram-cli 🟥 🟥 🟥
telegram-desktop 🟩 🟥 🟥
tigervnc 🟩 🟩 🟥
tilix 🟩 🟥 🟥
tinc 🟥 🟥 🟥
tinyemu 🟥 🟥 🟥
tinygo 🟩 🟩 🟥
tome2 🟥 🟥 🟥
trunk 🟥 🟥 🟥
tsocks 🟥 🟥 🟥
valgrind 🟥 🟥 🟥
vkmark 🟥 🟥 🟥
wasmedge 🟥 🟥 🟥
webkit2gtk-4.1 🟩 🟩 🟥
webkitgtk-6.0 🟩 🟩 🟥
weston 🟩 🟩 🟥
wiz 🟥 🟥 🟥
wlr-randr 🟩 🟥 🟥
wlroots 🟩 🟩 🟥
wxmaxima 🟩 🟥 🟥
wxwidgets 🟩 🟥 🟥
xf86-input-void 🟩 🟩 🟥
xf86-video-dummy 🟩 🟩 🟥
xfce4-screenshooter 🟩 🟥 🟥
xorg-server 🟩 🟩 🟥
xorg-xcalc 🟩 🟥 🟥
xrdp 🟩 🟩 🟥
xwayland 🟩 🟩 🟥
zellij 🟥 🟥 🟥
zenity 🟩 🟥 🟥
Totals 49 48 77 Only the lowest tier failed by each package is summed.

Contributor guide

Research direction
Pick a failing package from the list and examine its build log to identify the cause of failure.
Tech stack
shell
Domain
build systemdevops
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitDockerShell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60