Skip to content

0.9.5 --- follow openkal-musl 0.13.4, and run the release build on each host - #20

Merged
Sunrisepeak merged 2 commits into
mainfrom
follow-musl-0.13.4
Sep 14, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
follow-musl-0.13.4

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Carries openkal-musl 0.13.4 (mcpplibs/openkal-musl#33). This package's requirement on it is exact, so consumers reach its fixes only through this release:

  • openkal-macos 0.9.1 (0.9.1 --- the second register comes back from every call openkal-macos#20): every program built with --release faulted before main on macOS. The system call wrapper declared x1 an input only, this kernel returns a second value there, and the optimizer kept an argument in it across the call. Found through lsp-mcpp: its release server and a minimal import std program over 0.9.4 both stopped in kal_fs_preopen.
  • openkal-windows 0.7.4 (0.7.4 --- a named value is reported as it was set openkal-windows#23): environment values came back with forward slashes, so a program given a changed environment received ComSpec=C:/Windows/system32/cmd.exe and could not run a command through the interpreter.

Both were invisible to the dev profile, as openkal-windows 0.7.1's shortened arguments were. So besides the version:

  • openkal-musl = "0.13.4", version 0.9.5.
  • The macOS and Windows host jobs build examples/cxx with --release as well and require the same thread observations: The same program built with --release runs on this host.

…ch host

Carries openkal-musl 0.13.4: on macOS every program built with --release faulted
before main (openkal-macos 0.9.1), and on Windows a program given a changed
environment could not run a command through the interpreter (openkal-windows
0.7.4). The host jobs now also build examples/cxx with --release and require the
same observations, because both release defects in this chain were invisible to
the dev profile.
@Sunrisepeak
Sunrisepeak merged commit bba98e5 into main Sep 14, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant