GCC 16.1

Stack guide — GCC

When CPAN, pip, and npm do not cover your needs, GCC 16.1 is the same compiler that built the distribution itself. Compile C and C++ directly on the system:

gcc -O3 -march=x86-64-v3 -o /usr/local/bin/myapp myapp.c

# With libraries:
gcc -O3 -march=x86-64-v3 -o /usr/local/bin/myapp myapp.c -lmariadb -lssl -lcrypto

The -march=x86-64-v3 flag matches the distribution baseline — Haswell and later, with AVX2, BMI, and FMA. The compilation headers for every installed library are present; link against MariaDB, OpenSSL, zlib, or any other system library.

Clang, LLVM, and libclang 22.1.8 are also packaged as an alternative toolchain. Compiled output is ABI‑compatible with the GCC‑built distribution, so C and C++ can be built with either compiler.

Production

From /usr/local to stage4

The language managers — CPAN, pip, npm — are for development. You iterate, install modules, and test your application in /usr/local. When you are ready for production, build your application into stage4.

A stage4 package is reproducible, versioned, and built from source alongside the rest of the distribution. It has a pinned source archive, a SHA-256 digest, and a known licence. It is installed by the same deterministic toolchain that built MariaDB, nginx, and the kernel.

To add a package to stage4, create a recipe under packages/ and register it in stage4/dependencies.tsv. The build guide documents the full workflow — from recipe to signed APK index to bootable qcow2 image.

Build what you need. Then it is part of the distribution — not a runtime addition that drifts from machine to machine.