2.2GB for an image, and what do I get? GCC.
(pardon my informality)
that is ridiculous.
Once upon a time https://distrowatch.com/table.php?distribution=sorcerer sorcerer was a small source-based distribution, and it included all the things needed to compile more things, but not muche else, but was 200MB … 1/10th of the size.
# GDB can be included, even if only gdbserver is actually used.
util-linux-2.34
gmp-6.1.2
gdb-8.3
# Git could be included... for grabbing own projects to apply to the system.
openssl-OpenSSL_1_1_1c
util-linux-ng
libxml2-2.9.9
bison-3.4
curl-7.65.3
git-master
# tiny terminal editor
ncurses-6.1
readline-8.0
nano-4.3
# faster make systems
ninja-1.9.0
cmake-3.15.1
# goes up and down, unlike more
less-530
# extra things grabbed, incomplete though, ended up just disabling building docs for nftables.
asciidoc-8.6.9
texinfo-6.6
# iptables is obsolete/deprecated. nft allows building muitiple tables of rules for better application-grouped rules.
flex-2.6.4
expat-2.2.7
libmnl-1.0.4
libnftnl-1.1.3
nftables-0.9.1
# Things required to compile the kernel.
ed-1.15
bc-1.07
lz4-1.9.1
lzip-1.21
# No Node?
node (13.0.0-pre1/12.7.0)
npm-cli
# midnight commander and screen - terminal sharing/overloading utilities
slang-2.3.2
mc
screen-4.6.2
# Any hints on how to apply the binary mali kernel driver?
vulkansdk-1.1.114.0
mali-fbdev-vulkan
# included only because it was part of all added things (optional)
unixODBC-2.3.7
it’s actually not totally painful to build in a self-hosted environment.