release: reconcile syscall with origin; defer the native toolchain

syscall
  submodule/syscall had diverged from origin -- 18 local commits against
  19 on the remote, with matching subjects and different SHAs, i.e. the
  local branch had been rewritten at some point. Rather than force-push
  and discard 19 published commits, rebased local onto
  origin/submodule/syscall. git absorbed 16 duplicates by patch-id,
  leaving two genuinely local commits (NUMA support, which origin does
  not have at all, and the 0.3.2 version bump).

  Verified no work was lost: the rebased tree is byte-for-byte identical
  to the pre-rebase state apart from the Cargo.toml version line, and a
  backup/pre-rebase-* branch is kept. Two Cargo.toml conflicts were
  version-label collisions only, resolved to 0.9.1+rb0.3.1 mid-series and
  0.9.1+rb0.3.2 at the tip, per the Cat 2 convention. The push is now a
  fast-forward and the gitlink is updated to the rebased SHA.

native toolchain
  gcc-native and rust-native set to "ignore" -- explicit operator
  decision, 2026-08-03: 'Treat gcc-native/rust-native as a separate
  workstream, explicitly deferred by me, for now.' That is the one
  condition AGENTS.md ABSOLUTE RULE permits an exclusion under. It is not
  an agent-initiated removal, and not a repeat of the 'not needed for
  greeter proof' hand-wave that previously hid real breakage -- that
  suppression was reverted first, which is how the defects were found.

  binutils-native and llvm-native stay in the target; llvm-native is
  required for libclc and Mesa's iris/radeonsi CLC path. The recipes for
  the deferred pair are fixed and committed, not reverted.
This commit is contained in:
2026-08-03 19:41:49 +03:00
parent 472a58e001
commit cdb8f39661
2 changed files with 23 additions and 9 deletions
+22 -8
View File
@@ -262,16 +262,30 @@ redbear-meta = {}
redbear-power = {}
# Native build toolchain (Phase 3: GCC + binutils running on redox)
# All four are first-class members of this target. gcc-native was set to
# "ignore" and llvm-native/rust-native were commented out as "not needed for
# greeter proof"; both forms are forbidden by AGENTS.md § ABSOLUTE RULE —
# NEVER DELETE, NEVER IGNORE, NEVER COMMENT OUT and by local/AGENTS.md
# § "No 'build-excluded until ported' packages". A package that does not build
# gets ported, not excluded.
gcc-native = {}
#
# binutils-native and llvm-native BUILD and stay in the target. llvm-native in
# particular is required, not optional -- it supplies the host LLVM dev tree
# that libclc and Mesa's iris/radeonsi CLC path consume.
#
# gcc-native and rust-native are DEFERRED — explicit operator decision,
# 2026-08-03: "Treat gcc-native/rust-native as a separate workstream,
# explicitly deferred by me, for now."
#
# This is the one condition AGENTS.md § ABSOLUTE RULE permits an exclusion
# under ("the ONLY acceptable time ... is when the user explicitly and
# directly requests it"). It is NOT an agent-initiated removal, and it is not
# the "not needed for greeter proof" hand-wave that previously excluded these
# and hid real breakage — that suppression was wrong and was reverted first,
# which is how the defects below were found at all.
#
# Everything discovered while getting them this far is recorded in
# local/docs/NATIVE-TOOLCHAIN-WORKSTREAM.md, including the seven fixes already
# landed and the exact point the work stopped. Re-enable by uncommenting; the
# recipes are fixed and committed, not reverted.
gcc-native = "ignore"
binutils-native = {}
llvm-native = {}
rust-native = {}
rust-native = "ignore"
# Desktop fonts and icons
dejavu = {}