ci: bump zig 0.13→0.16 for cross-build release jobs (FreeBSD OpenSSL link) - #3
Closed
paul-hammant wants to merge 1 commit into
Closed
ci: bump zig 0.13→0.16 for cross-build release jobs (FreeBSD OpenSSL link)#3paul-hammant wants to merge 1 commit into
paul-hammant wants to merge 1 commit into
Conversation
The aether toolchain's FreeBSD/tier-2 cross-link path is written for Zig 0.16; on 0.13 a FreeBSD cross link (the aeo CLI, which imports secrets -> std.cryptography -> OpenSSL) dies `error: libc not available`. Matches the bumps in aether-crossbuild (deps.lock) and aether (ae_cross.c tier-2 fix + windows.yml). Also updates the archive name — 0.16 is zig-x86_64-linux-<ver> (arch before os), 0.13 was zig-linux-x86_64-<ver> — in both the crossbuild toolchain path and the agent job's self-contained fetch. Does NOT yet flip build-freebsd load-bearing: leaving continue-on-error and the AEO_FREEBSD_MIN_AE gate until the aether ae_cross fix is released and pinned (tracked in asks/aeo-cli-freebsd-cross-openssl.md). This is the toolchain-pin half. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Collaborator
Author
|
aeo goes straight to main — merging the branch directly instead of via PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pinned Zig for the cross-build release jobs from 0.13.0 to 0.16.0.
Why
The aether toolchain's FreeBSD/tier-2 cross-link path (
tools/ae_cross.c) iswritten for Zig 0.16. On 0.13, a FreeBSD cross-link dies with
error: libc not available/cannot find entry symbol _start— which is whatblocks the aeo CLI's FreeBSD asset (it's the first FreeBSD-cross target that
pulls OpenSSL, via
import secrets→std.cryptography). It is not actuallycrypto-specific; any FreeBSD cross-link fails on 0.13. Diagnosed and fixed
upstream:
deps.lockzig 0.13.0 → 0.16.0 (merged to main).ae_cross.ctier-2 fix (link staged libs by absolute path, onlywhen the program uses them — 0.16 hard-errors on the danglers 0.13 tolerated)
windows.ymlpin — FreeBSD tier-2 cross-link under Zig 0.16: link staged libs by path, only when used aether#1930.What this PR changes
release-aeo.yml: crossbuild toolchain pathzig-linux-x86_64-0.13.0→zig-x86_64-linux-0.16.0(0.16 renamed the archive: arch before os).release-aeo-agent.yml: same toolchain path, plus the agent job'sself-contained fetch (
ZIG_VERSION0.13.0 → 0.16.0 and thezdirnaming).What this PR does NOT do (yet)
It does not flip
build-freebsdload-bearing.continue-on-errorand theAEO_FREEBSD_MIN_AEgate stay until the aetherae_crossfix (#1930) isreleased and pinnable — the two-line follow-up tracked in
asks/aeo-cli-freebsd-cross-openssl.md. This is the toolchain-pin half; thegate-bump half lands once there's a released ae version carrying the fix.