You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Released macosx-arm64 binaries carried LC_BUILD_VERSION minos=15.0 and
dynamically linked the SYSTEM /usr/lib/libc++.1.dylib, so they only ran
on macOS 15: dyld refuses older minos, and lowering minos alone dies at
launch on macOS 14 with a missing libc++ symbol
(__ZNSt3__119__is_posix_terminalEP7__sFILE — std::print support added in
LLVM-18-era libc++; verified on macos-14 CI).
- flags.cppm: implement staticStdlib (the manifest default, previously
silently ignored on the clang route) for the macOS link path — link
LLVM's own libc++.a/libc++abi.a via -nostdlib++ instead of -lc++,
falling back to -lc++ when the archives are absent. Mirror
MACOSX_DEPLOYMENT_TARGET onto compile and link command lines so ninja
commands don't depend on env propagation.
- cli.cppm: fold MACOSX_DEPLOYMENT_TARGET into the BMI fingerprint —
the deployment target changes the effective compile triple
(arm64-apple-macosxNN), and a std.pcm built for one target cannot be
loaded by a TU compiled for another (config-mismatch observed on CI).
- main.cpp: __APPLE__ exit guard (_Exit after stream flush) — static
libc++'s static destruction can SIGABRT on exit; same guard xlings
uses.
- release.yml (macos job): MACOSX_DEPLOYMENT_TARGET=11.0 + staged-archive
ldflags injection for the self-build (the bootstrap mcpp predates this
change), with minos/no-dylib assertions.
- version 0.0.50.
Design: xlings .agents/docs/2026-06-05-macos-min-version-support.md
0 commit comments