Repository navigation
[CANARY — DO NOT MERGE] gcc 15.2.0 → 16.2.0 world build (pm#1182) - #1340
bryan-minimal wants to merge 50 commits into
Conversation
World-build canary to collect the gcc 16 FTBFS list. - version 16.2.0; source from mirrors.kernel.org (not yet mirrored to gs://minimal-staging-archives). sha256 e6738e29... matches the ftp.gnu.org tarball whose .sig verifies against Richard Biener's key 13975A70E63C361C73AE69EF6EEB81F8981C74C7 from the GNU keyring. - build.sh: gcc-16.2.0 dir names; drop the libgomp -Wno-error=discarded-qualifiers hatch (affinity-fmt.c:330 is `const char *q` in 16.2.0). - replace_on_cycle seeds unchanged (gcc 15.2.0 compiles gcc 16 once). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
…6 FTBFS) gcc 14.2.0's libcody does `words.emplace_back (u8"")`, which no longer compiles once the host compiler defaults to C++20 (u8"" is const char8_t[]). gcc 16.2.0's libcody casts it, so move the cross compiler to the same gcc release as the native one (latest-version policy) instead of pinning -std=gnu++17. - gcc 16.2.0: same tarball/sha256 as packages/gcc (e6738e29..., .sig verified against 13975A70E63C361C73AE69EF6EEB81F8981C74C7). - newlib 4.6.0.20260123: sha256 6ff27e3b...; its sha512 matches sourceware.org/pub/newlib/sha512.sum (newlib publishes no signature). - t-rmprofile is unchanged between 14.2.0 and 16.2.0 except the copyright year, so the multilib sed still applies; every newlib configure option the recipe passes still exists in 4.6.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gcc 16 adds -Wsfinae-incomplete and new -Wunused-but-set-variable / -Warray-bounds diagnostics that cbmc 6.11.0's -Werror build promotes to errors. Upstream fixed them in #9024 (merge 4b26409c, 2026-10-02), after 6.11.0, which is still the latest release and what Kani 0.68.0 pins, so carry that PR as a patch until the next release. It applies cleanly to the 6.11.0 tag (git apply --check) and is behaviour-neutral (warning-path cleanups and a dead counter), so it also builds under gcc 15. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Repack libgcc_s, libstdc++, libgomp, libatomic, libgfortran and (amd64) libquadmath from the gcc build dep, byte for byte, under gcc's output names, with runtime_deps [glibc]. A subsetOf gcc dep fetches the whole compiler and its runtime_deps; this does not. Own replace_on_cycle on the gen-13 gcc objects. Consumers are not migrated yet (gominimal/inbox#1261). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every other package record ends `} | BuildSpec`. Without it the record
has no `ty = 'Builder`, so `subsetOf gcc-runtime [...]` fails minimal's
Subsettable contract ("Expected Input type").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A subset fetches the parent's whole build artifact and pulls in its runtime_deps, so `subsetOf gcc ["libgcc"]` cost every consumer the whole compiler plus gmp, mpc, mpfr, zlib and zstd. - All 138 `subsetOf gcc` runtime sites (137 build.ncl files plus llvm/versioned.ncl, including boost's multi-line arch-match form) now take `subsetOf gcc-runtime` with the same outputs. That includes gmp, ncurses and binutils, which sit under base, coreutils and bash. The gcc import is dropped where nothing else uses it (123 files) and kept where build_deps or test_deps still do (15). - openblas: `libs` -> ["libgcc", "libgfortran"] plus libquadmath on amd64. stlink: `libs` -> ["libgcc"]. Both are marked TODO(readelf). - Whole-gcc runtime deps that only need the libraries: chromium-headless-shell-bin, helix, hex-patch, nushell, uv and zellij -> ["libgcc"], z3 -> ["libgcc", "libstdcpp"]. chromium is marked TODO(readelf both arches). - kani and verus-latest run the compiler, so their runtime gcc + binutils become `toolchain`, which both already import for build_deps. Their redundant gcc subset line is dropped. No `subsetOf gcc` remained in any build_deps, test_deps or replace_on_cycle block, so none was left behind. gcc, toolchain and gcc-arm-none-eabi are untouched. Each changed file is `nickel format` clean and evaluates on amd64 and arm64. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This guard is blocking. It reads every .ncl under packages/ and fails on `subsetOf gcc` in any form, or on a whole `gcc`, inside a runtime_deps field. Breaker runtime_deps are included. The `gcc` it means is whatever identifier binds gcc/build.ncl, so a renamed binding or an inline import is still caught. Comments and strings are ignored, and gcc-runtime and gcc-arm-none-eabi don't match. Only `toolchain` may take whole gcc. The allowlist fails on a stale entry. Exit 2 (UNVERIFIED) means the tree is missing, or too few runtime_deps fields were parsed to trust the result. The unit tests include negative controls: every rejected form must be caught. Mutating the guard (its matcher, comment stripping, or the stale-entry check) turns them red. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The subsets section said subsets exist "to avoid any user of a package needing to download a whole gcc". That is false. The client fetches the parent's whole artifact and cuts the subset out locally, and the closure takes in the parent's runtime_deps. The section now says so, and points to gcc-runtime and its guard. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
libgfortran.so.5 is 8.35 MB, 64% of gcc-runtime (anvil, amd64), and only openblas (and numpy through it) loads it. A package is fetched whole, so every C/C++/Rust closure would download it for nothing. gcc-runtime-fortran repacks it from gcc and takes subsetOf gcc-runtime ["libgcc"] (+ libquadmath on amd64, which boost also uses, so it stays in gcc-runtime). openblas takes gcc-runtime ["libgcc"] and gcc-runtime-fortran ["libgfortran"]. Bryan approved the split (inbox#1261). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…annot fail Review on inbox#1261 (minimalboarding): - gcc-runtime's replace_on_cycle repacks the same gominimal/bootstrap objects as gcc's. Two copies drift on the next repin, leaving an older gcc's libstdc++ in roots beside the real gcc's. gcc_runtime_guard.py now fails when the two breakers' (url, sha256) pins differ or can't be read (3 tests; a one-character drift on the real tree fails). - cxx_exception_unwinds had gcc in test_deps, so gcc's own libstdc++ and libgcc_s answered it and it passed with gcc-runtime empty. Dropped; loads_without_gcc (bash-bootstrap only) is the test that proves the package. - Comments: output names (not globs) match gcc's; why the breaker has no runtime_deps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bryan's plan: develop gcc-runtime stacked, get one combined world-build signal from this canary, then land gcc-runtime as separate commits inside the real gcc 16 PR so the world rebuild is paid once. Merged, not rebased, to keep the canary's history without a force push. Brings pkgs main up to ca566dc and the gcc-runtime branch at d3ceedc (gcc-runtime, gcc-runtime-fortran, 138 consumers moved, gcc_runtime_guard.py, AGENTS.md). Clean merge; the guard passes and gcc, gcc-runtime(-fortran), openblas, gmp, ncurses, binutils, zellij and cbmc evaluate on both arches (local nickel). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From minimalboarding's read of minimal main 9396210bb (inbox#1261): - A pure prebuilt is extracted straight into its cache entry; output globs are not applied (crates/op/src/specs.rs materialize_prebuilt). So on a cycle edge gcc-runtime (prebuilt) is the whole gen-13 gcc tree, compiler included. A subset cuts only its globs (subsets.rs), but a whole gcc-runtime dep would link all of gcc 15.2 into that root. The guard now rejects a bare gcc-runtime in runtime_deps (whole-gcc-runtime rule, with a violation case and a multi-line subset clean case). - subsets.rs unwraps the requested output, so asking the breaker for an output it does not declare panics. It now declares libquadmath on amd64, matching the real spec (the amd64 object ships it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… 16 canary Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Published llvm 23.1.5 (amd64, pkgs ca566dc): libLLVM.so.23.1, lld and llvm-config NEED libzstd.so.1, but llvm never declared zstd. It arrived only because `subsetOf gcc` inherits gcc's runtime_deps (gmp, mpc, mpfr, zlib, zstd). gcc-runtime does not, so after the migration clang, lld, rustc and anything loading libLLVM would fail in a closure without zstd. Found by minimalboarding from the artifact's ELF dynamic section. llvm/versioned.ncl (llvm-21/22/23) gets the same dep. A fleet-wide audit of the same class is running. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Same class as llvm (inbox#1261), from minimalboarding's DT_NEEDED audit of the ca566dc amd64 artifacts against the branch closures: - python: lib-dynload/_zstd NEEDs libzstd.so.1. It arrived via bash -> ncurses -> subsetOf gcc -> gcc's runtime_deps; with ncurses on gcc-runtime, `import compression.zstd` would fail. zstd is already on the gcc bootstrap cycle (gcc depends on it; it has a prebuilt breaker). - llvm-bootstrap: clang-21 and its tools NEED libzstd.so.1. Build-closure tools audited clean: gawk(-bootstrap), coreutils, perl, cmake, binutils, rust, rustc-1.98.1, make, tar, grep, sed, bash, ninja, meson, pkgconf, toolchain, glibc and others. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…16 canary Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
minimalboarding's DT_NEEDED audit of all 145 migrated packages (amd64, ca566dc artifacts) found five more binaries that load a library their recipe never declared, hidden by subsetOf gcc inheriting gcc's runtime_deps: - usr/bin/lsd, usr/bin/tuicr, usr/bin/teamtype, usr/bin/nu: libz.so.1 - mesa usr/lib/libgallium-26.3.0.so: libzstd.so.1 These are latent bugs on main too; the declared dep is correct either way. The other 137 audited packages are clean on the eight gcc-inherited sonames. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…: zstd Second audit pass (indirect gcc consumers, amd64 ca566dc artifacts): - usr/bin/cabal NEEDs libz.so.1; it came via gmp -> subsetOf gcc. cabal is in the build closure of every Haskell package. - gcc-arm-none-eabi's cc1/lto1/lto-dump NEED libgmp, libmpfr, libmpc and libzstd; a compiler that never declared a compiler's deps. They came via bash -> ncurses -> subsetOf gcc. zlib still comes through binutils-arm-none-eabi. - mariadb usr/lib/plugin/zstd.so NEEDs libzstd.so.1 (optional plugin). Latent on main as well (inbox#1261). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cc 16 canary Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
usr/bin/stack NEEDs libz.so.1; it came only through gmp -> subsetOf gcc, like cabal. Last hit of minimalboarding's two-pass DT_NEEDED audit (301 packages with a published amd64 artifact; 12 recipes needed a declaration, plus mariadb's optional plugin; 287 clean). inbox#1261. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gcc 16's libstdc++ no longer pulls <cstdint> in transitively, so bindings/c c_workloads failed with "'uint64_t' does not name a type" on both arches (canary run 2b69a34d). Fail closed if the include is missing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The import-line checker failed it in the lab run at 126686e. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… 34ab070b) - libvpx, maki, hex-patch take libstdcpp; gn, ninja take libgcc. Each loaded the library it did not declare: subsetOf gcc fetched the whole compiler and hid the gap, gcc-runtime ships only the declared outputs. - gcc-runtime ships libssp (stlink's binaries and libstlink NEED libssp.so.0). - boost declares openssl (libboost_cobalt_io_ssl NEEDs libssl/libcrypto.so.4). - import lines: canonical order for chromium-headless-shell-bin, nushell, hex-patch; kani and verus-latest no longer import an unused subsetOf. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gcc 16 defaults to gnu++20, so abseil pinned ABSL_OPTION_USE_STD_ORDERING 1 into the installed options.h and -std=c++17 consumers failed on std::partial_ordering (canary run 34ab070b). Pin C++17 (what gcc 15 built) and fail closed unless options.h pins ORDERING 0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run 7e4acbc4 built gcc-runtime twice (breaker pass, then real) and the
{libgcc, libstdcpp} subset stayed pinned to the gcc 15 breaker-pass repack
(minimal orchestrator state.rs:396-426, per minimalboarding), so
mathlib-oleans loaded a libstdc++ without GLIBCXX_3.4.35. With the real
gcc-runtime cached, this run should cut every subset from it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gcc-runtime's build root also holds its own cycle breaker (a bootstrap gcc, via gcc -> gmp -> gcc-runtime), and first-wins by spec-hash order picks between the two gccs' usr/lib files. On arm64 the gcc 16 canary (pkgs#1340 run 7e4acbc4) shipped the gen-13 gcc 15 libstdc++.so.6 and libgcc_s.so.1, and lean failed on GLIBCXX_3.4.35. - gcc stages its shared runtime libraries again under usr/lib/gcc-runtime-stage, a path no bootstrap object ships. - gcc-runtime and gcc-runtime-fortran copy from there (stage.sh). With no stage, gcc is the breaker (first pass of the cycle) and they copy usr/lib as before. - Either way each versioned library must have exactly one real file and its SONAME must link to it, so mixed gccs fail the build. - The guard keeps the two stage.sh copies byte-identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d168779c) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
libopenblasp-r0.3.34.so NEEDs libgfortran.so.5, libm, libc and the loader on both arches, in both the gcc 15 build and the gcc 16 canary (pkgs#1340 run d168779c). Nothing in it NEEDs libgcc_s, so the direct gcc-runtime libgcc edge goes; libgfortran's own libgcc_s and libquadmath (amd64) still come through gcc-runtime-fortran, so the closure is unchanged. Clears the last TODO(readelf) on this branch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ey NEED The gcc-runtime output audit (readelf over main's artifacts, both arches) found two consumers whose closure lacked an output they load: - llvm-bootstrap: clang-21 NEEDs libstdc++.so.6; only libgcc was declared. - ngspice (--enable-openmp): NEEDs libgomp.so.1, libstdc++.so.6 and libgcc_s.so.1; it had no gcc-runtime dep and got them only from whole gcc in its main closure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…bytes The gcc 16.2 canary built gcc twice, and gcc-runtime shipped files that differ from gcc's at the same /usr/lib paths (libgcc_s.so.1, libstdc++.so.6.0.36, libgomp.so.1.0.0 on both arches; also libatomic and libssp on arm64). binutils, gmp and ncurses are in gcc's build graph and depended on gcc-runtime. Cycle breaking therefore resolved gcc one way on its own and another way inside gcc-runtime's build, so gcc-runtime copied a second gcc build. On arm64 that build was assembled by the binutils 2.41 breaker (published gcc: 2.47). Under the arch registry spec (registry-model.md §12) that is a file conflict in any box holding both packages. Equal files are not a conflict. Only the C++ add-ons needed gcc-runtime (DT_NEEDED of the main artifacts). A DT_NEEDED sweep of all 70 packages that import binutils, gmp or ncurses found one user: maude (libgmpxx). - ncurses: --without-cxx-binding (libncurses++w; nothing links it). - binutils: --disable-gprofng (the only C++ part; nothing uses it); drop the gprofng outputs. - gmp: --disable-cxx. The C++ interface moves to a new gmpxx package that builds the same release with --enable-cxx and keeps only libgmpxx.so*, gmpxx.h and gmpxx.pc. Its build fails if its version differs from the gmp build dep's. maude takes gmpxx. - The three drop their gcc-runtime runtime dep. - gcc_runtime_guard.py rule 4: fail if gcc's build graph (outside tests and replace_on_cycle) reaches gcc-runtime or gcc-runtime-fortran, and name the path. Negative control: on the previous commit it reports gcc -> gmp -> gcc-runtime. Four new tests; 22 pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in 82a4020 (openblas deps), 34630f9 (llvm-bootstrap and ngspice outputs) and 5998d93: ncurses without the C++ binding, binutils without gprofng, gmp without C++ plus a gmpxx package for maude. gcc then builds once and gcc-runtime copies its exact bytes (arch registry spec, registry-model.md section 12). Clean merge; gcc_runtime_guard passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Canary re-run at The last run (d168779c / aafd9abb) passed, but gcc-runtime's libraries differed from gcc's at the same
Under the registry spec (arch#183, Cause: binutils, gmp and ncurses are in gcc's build graph and depended on gcc-runtime. Cycle breaking therefore resolved gcc differently inside gcc-runtime's build, so gcc was built twice. On arm64 the second build used the binutils 2.41 breaker. Fix (5998d93, merged in here):
What this run should show: one gcc build per arch, and gcc-runtime's files byte-identical to gcc's. I'll compare the artifacts when it finishes. Details: gominimal/inbox#1267. 🤖 Generated with Claude Code |
main gained node-26.12.1 (#1494) with subsetOf gcc in its runtime_deps; it takes the same libgcc and libstdcpp outputs from gcc-runtime, as node and node-lts do. gcc_runtime_guard passes on the merged tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With --disable-gprofng nothing is installed under /etc, so the etc/* glob matched nothing and the canary failed (5d6cdd9, both arches). The main artifact's only etc file was etc/gprofng.rc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gmp is built --disable-cxx now, and the canary (ffdb3c3) failed in libpoly: polyxx includes gmpxx.h. The DT_NEEDED sweep missed it because the use is header-only (mpz_class inlines; nothing links libgmpxx). A scan of the C++ gmp importers' pinned sources found the same in cvc5 (src/util/gmp_util.h, integer_gmp_imp.h, ...), which cvc5-ff shares. cocoalib needs gmpxx only for Frobby, MathSAT or Normaliz, none enabled; gdb and lean do not use it. - libpoly: gmpxx build dep, and runtime dep (its polyxx headers include gmpxx.h). - cvc5, cvc5-ff: gmpxx build dep. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
These NEED libstdc++ and libgcc_s but got them only through gmp or ncurses (directly, or via python/readline), whose gcc-runtime dep is gone so gcc's build graph no longer reaches gcc-runtime. The canary (8c6736e) caught gdb: "libstdc++.so.6: cannot open shared object file". The output audit (audit_outputs.py with --main-rt, both arches) found the rest: - gdb: + libgcc, libstdcpp (had libatomic) - gettext: + libgcc, libstdcpp (libasprintf; had libgomp) - numpy: + libgcc, libstdcpp - btop, mariadb, gnutls (libgnutlsxx), gcloud (bundled python): + libgcc, libstdcpp After: the only MISSING rows are binutils, gmp and ncurses, whose main artifacts still hold the C++ files those packages no longer build. gcc_runtime_guard passes (rule 4: none of these is in gcc's build graph). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
gcc-runtime now copies the published gcc's exact bytes. Compared every shared path (type, mode, sha256 or link target) between the published gcc and the gcc-runtime packages, using the artifacts from run 9ee7cf5e. The 8c6736e run reused them from cache.
The gcc artifacts are byte-identical to the previous canary's. That confirms gcc builds once and gcc-runtime no longer gets a second gcc build (5998d93, guard rule 4). 8c6736e run (7af95c60): the world built on both arches (197 amd64 and 244 arm64 builds). All 8 check failures were packages that got libstdc++ only through gmp/ncurses:
Now at 58e8a13: merges d16dd32, which declares gcc-runtime in those packages plus gettext and gcloud. The output audit is clean on both arches, apart from the C++ parts removed on purpose. 🤖 Generated with Claude Code |
The proposed registry spec gives each output its own tarball, and its gcc
example splits gcc into 25 outputs with no file in two of them
(specs/registry/nickel/examples/packages/gcc/build.ncl at 5ab05d1). gcc's
outputs change hash for nearly every package, and the spec's owner wants
that change in a rotation that rebuilds the world anyway; the gcc 16 bump
is one.
The old catch-alls libs (usr/lib/**/*.{a,o,so*}) and libs_all (usr/lib/**)
put 101 files in two or three outputs. Now 27 outputs (26 on arm64, no
libquadmath), in today's run-time kinds:
- libraries: libgcc, libstdcpp, libgomp, libatomic, libgfortran, libssp,
sanitizers, libs_other, libquadmath (amd64), runtime_stage (the copy
gcc-runtime repacks);
- the compilers' parts: bins, libexec_bins, libexec_libs, plugins,
install_tools, liblto_plugin, gcc_objects, gcc_headers,
gcc_install_tools, includes, static_libs, specs, share_data;
- the spec's dev/doc files, as data until min has those kinds: ltconfigs,
lto_plugin_ltconfig, plugin_dev, mans.
Checked against the real file lists: gcc 16.2.0 canary artifacts
(311b5b39 amd64, 1,823 files; ff6a4e54 arm64, 1,700) and main's gcc 15.2.0
ones. Each file is in exactly one output and no output is empty (except
runtime_stage on main's gcc 15, which predates the stage). gcc 16 adds
libgcc_s_asneeded.so and libatomic_asneeded.so (linker scripts), so those
globs are libgcc_s*.so* / libatomic*.so* with allow_data. Differences from
the example: libssp is its own output (stlink needs only it); libs_other is
libcc1 and libitm. No package outside gcc names a gcc output (all 42
importers take gcc whole), so nothing else changes. Evaluates on both arches
(local nickel shim); gcc_runtime_guard passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 outputs (26 on arm64), no file in two of them, checked against this canary's gcc 16 artifacts; rides this world rebuild. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fsf-funding.7, gfdl.7 and gpl.7 are generic gcc pages; gcc ships them at the same paths from a different build, a file conflict under the registry spec (arch#183 model section 12). Found by the build-servers amd64 file-list survey of pkgs b891179. build.sh already dropped share/info for this reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lowercase names sort first and alphabetically: standaloneTest before subsetOf. Canary 230721a failed only this check (import line), on both arches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both rebuild the world, so they ride the same rotation as gcc 16 instead of each costing one of their own. - #1499: amd64 binutils breaker and ghc-9.6.7 onto gen-16's plain-loader objects (binutils-2.46-glibc-seed, ghc-9.6.7). - #1535: arm64 gcc breaker onto gen-17's gcc-15.2.0-glibc-seed. gcc-runtime's breaker moves with it, since gcc_runtime_guard.py requires the two pins to match. All three objects exist in gs://minimal-bootstrap. #1499's build was green. #1535's failed only on tmd's zig fetch from deps.files.ghostty.org (connection reset), which is unrelated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Under the registry spec (gominimal/arch#183, D-24) a prebuilt keeps only the files its output globs name. The OQ-42 survey found 10 breakers that would lose files. This fixes the ones that matter: - bash-bootstrap, bzip2: `outputs = {}` became the real spec's outputs, shared through a let as gcc-runtime does. They had kept nothing. - binutils, arm64: target_tools for usr/aarch64-linux-gnu, the as and ld that gcc runs by target path. - attr: etcs for etc/xattr.conf, read by libattr. - glibc: bedrock for the glibc-bedrock-2.42 sysroot, which gen-13 tools may still load through, and, on arm64, lib64 for the second copy of the libraries and crt objects under usr/lib64. The survey had counted the lib64 files as bedrock. Measured against the 2026-11-14 artifacts and the newly pinned gen-16 and gen-17 objects, every breaker now loses 0 files except var/db/Makefile in glibc arm64 (nss database helper, unused at run time). grep, sed, make, tar and gzip still drop locale, man and info files, which become doc under D-25. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…308f31) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
230721a built the world on both arches with the registry spec's 27 gcc outputs. Of 17,160 checks, 4 failed, all one cause: the import line in btop and gnutls was out of canonical order ( Now at
The gcc-runtime guard passes. #1499 and #1535 can close once this lands as the real gcc 16 PR. 🤖 Generated with Claude Code |
|
🤖 Generated with Claude Code |
Caution
CANARY. DO NOT MERGE, DO NOT APPROVE, NEVER ADD TO THE MERGE QUEUE.
This PR exists only so build-bot runs a full world build with gcc 16.2.0 as the default compiler. It is a draft on purpose and will be closed once the FTBFS list is collected. The real flip will be a separate, human-authored PR queued alone.
Update 2026-11-14: gcc-runtime merged in (gominimal/inbox#1261)
Bryan's plan: develop the gcc-runtime split stacked, take one combined world-build signal from this canary, then land gcc-runtime as separate commits inside the real gcc 16 PR, so the world rebuild is paid once. Branch
gcc-runtimeis merged into this canary (merged, not rebased, so there's no force push). This also brings pkgs main up to ca566dc.The merge adds:
packages/gcc-runtime: gcc's shared runtime libraries (libgcc_s, libstdc++, libgomp, libatomic, amd64 libquadmath), repacked byte for byte from gcc under gcc's output names, with runtime_deps[glibc]and its own prebuilt breaker on the same gen-13 objects as gcc's.packages/gcc-runtime-fortran: libgfortran, for openblas only.subsetOf gcc [...]runtime deps moved tosubsetOf gcc-runtime [...], gmp, ncurses and binutils included. Seven whole-gcc runtime deps moved to library subsets; kani and verus-latest moved totoolchain..github/scripts/gcc_runtime_guard.py: rejects a runtime gcc subset, a whole gcc (toolchain excepted), or a whole gcc-runtime, and requires gcc-runtime's breaker pins to equal gcc's.Why: a subset fetches the parent's whole artifact and inherits its runtime_deps. So every libgcc consumer downloaded all of gcc (anvil amd64: 341.6 MiB unpacked / 116 MiB zstd) for libraries now about 4 MiB.
What to look at in this run, beyond the gcc 16 FTBFS list:
# TODO(readelf)edges are chromium-headless-shell-bin, openblas and stlink.libstdc++.so.6/libgcc_s.so.1. Layers link first-wins in cache-path order, so a root holding real gcc 16 and the 15.2-object gcc-runtime breaker could load 15.2's libstdc++ (missing GLIBCXX versions). Any hit should be listed. See gominimal/inbox#1226.Purpose
Step 4 of gominimal/pkgmgr-rs#1182: collect the complete list of packages that fail to build (FTBFS) when the default compiler
packages/gccmoves from 15.2.0 to 16.2.0. gcc is in every package's reverse import closure (616/616), so this PR rebuilds the whole world.What changed
Only
packages/gcc/:build.nclversionis now 16.2.0.https://mirrors.kernel.org/gnu/gcc/gcc-16.2.0/gcc-16.2.0.tar.xz, sha256e6738e29597f733270731aa90600f37ffdc045079dfc27ec7e8192cc81085c3e.build.shgcc-16.2.0directory names replace the hardcodedgcc-15.2.0.-Wno-error=discarded-qualifiershatch is dropped (the CFLAGS/CXXFLAGS/*_FOR_TARGETexports and their comment).libgomp/affinity-fmt.c:330is alreadyconst char *qin 16.2.0.replace_on_cycleseeds (gcc-15.2.0) stay as they are. gcc 16 is compiled once by the 15.2 seed, and gcc 16 needs only a C++14 host.lib64sed targets int-linux64/t-aarch64-linuxare still present.Source verification: the tarball's sha256 is identical from ftp.gnu.org and mirrors.kernel.org. Its
gcc-16.2.0.tar.xz.sigverifies against GCC release key13975A70E63C361C73AE69EF6EEB81F8981C74C7(Richard Biener) fromgnu-keyring.gpg.sqtherefore only authenticates it with--policy-as-of 2014-01-01.data/signing_policies.tomlever covers gcc.⚠ Mirroring needed before any real flip. Every other gcc source lives at
gs://minimal-staging-archives/gcc-%{version}.tar.xz. This canary points at upstream because the tarball could not be uploaded from here. The flip PR must mirror it first and restore the gs:// URL.Deliberately left alone (track for the flip)
stacks/make/stack.nclstill applies-Wno-error=discarded-qualifiersfleet-wide. It is documented as durable because it is about glibc 2.43+ headers, not gcc.gcc-arm-none-eabi: 14.2.0. libcodyu8/ char8_t, plus the safe-ctype vs<memory>poisoning. The fix is to bump it to ≥ 14.4.0.cbmc6.11.0 (andkani): upstream-Werrorhitssfinae-incomplete/unused-but-set-variable. The fix is to backport Fix GCC 16 warning-as-error build failures diffblue/cbmc#9024.Local sanity build: not done
I couldn't run a local
min package build gccfirst, so gcc 16.2.0 itself is unproven until this run. Activating apkgbuildsession on this worktree means rebuildingbase's closure, because gcc changed. That rebuild needs the bedrock prebuilt seeds (gcc (prebuilt),zlib (prebuilt)) fromgs://minimal-staging-archives. minvmd 0.7.3-rc1's node-plane egress baseline drops those connections (dropped a node-plane frame ... toward an address no baseline entry pinned), so session spawn failed withcannot connect to endpointon storage.googleapis.com.If the bot fails on
gccitself, it fails early and cheaply, and I'll fix it on this branch.How results will be triaged
operator!=)-WerrorwarningsAC_PROG_CXXdowngrade probe-lgcc_s_asneeded)-Wno-error=/-std=pin) that also builds under 15.2.FTBFS log (running)
The bot stops an arch's whole run at the first failed package (the minimal orchestrator aborts on the first error and has no keep-going mode), so failures surface one per run. Each fix is one commit on this branch, so it can be cherry-picked into its own PR.
u8""into std::string (gcc 14.2.0 source)-Wsfinae-incomplete/-Wunused-but-set-variable/-Warray-boundsunder-Werror🤖 Generated with Claude Code