[metif12]

build.vsh now has a 'vinix' key in ignore_dirs. It lists only uptime, rather than sharing the macOS list: stat and sync are excluded on macOS because the BSD syscall surface differs from Linux, and Vinix follows POSIX closely enough that both build there. Without the key, the dictionary lookup fell through to an empty list — which read as "build everything" and would have attempted the Windows-excluded Unix set alongside it.

A CI job cross-compiles all 87 tools for the target, since GitHub has no Vinix runner.

That job is not decoration. It is what found that timeout did not compile on any Unix. timeout.v passed mut &p to terminate_process, which only the Windows variant declares as mut; the _nix and _default variants rejected it. Linux, macOS and Vinix were all broken while Windows CI was green, and the -Wimpure-v gate never saw it because only Windows builds the directory. All three variants now take mut p &os.Process so the call site is uniform, and the Windows comment explaining why the pointer is mutable is kept rather than deleted as redundant.

V's side needed nothing: $if vinix, _vinix.c.v file suffixes and -os vinix all already work, and _nix.c.v files are selected on Vinix because the suffix allowlist only excludes them on Windows. I verified that with a probe rather than assuming it.

Verified: 87 of 87 tools cross-compile for Vinix, timeout builds for all four targets (windows, linux, macos, vinix), and the Windows build is unchanged.

Two things I want to flag, not bury

The CI job parses build.vsh with shell text tools to read the ignore list, so the two cannot drift. That parsing is now verified: it extracts exactly uptime, skips exactly 1 of 87, and drops the key word itself. But it is still a shell grep reading a V source file, which is a real fragility — a restructured map literal would break it. A stronger design would have build.vsh emit the list on request (v run build.vsh --print-ignored), which is a bigger change than this PR should carry. Worth a follow-up.

It cross-compiles; it does not run. There is no Vinix runner, so nothing in CI executes the resulting binaries, and a tool that compiles but misbehaves on Vinix will still pass. That is a meaningful gap, and the job says so in a comment rather than implying coverage it does not have.

[metif12]

Two things changed after rebasing onto main, and one claim in this description is now wrong.

The timeout half moved to #263

This branch was written against the tree before c6cbc320b6, and fixed the then-inconsistent timeout by making all three terminate_process variants take mut p &os.Process. That fix is still correct and is now needed on main for a stronger reason than the one given here — but main's subsequent commit broke the Windows build of timeout outright:

src/timeout/timeout_windows.c.v:13:3: error: `p` is immutable, declare it with `mut` to make it mutable

So the fix is no longer part of this PR; it is #263, on its own so it can land ahead of this one and so main stops shipping a build break. Once #263 merges, this branch's src/timeout commit rebases away and this PR is left carrying only the Vinix build target — .github/workflows/ci.yml and build.vsh. I have confirmed that by rebasing onto #263: the diff comes out as exactly those two files.

The description line "the Windows build is unchanged" is no longer true and I am not able to re-verify the "87 of 87 tools cross-compile for Vinix" claim from here — there is no Vinix toolchain on this machine, and the vinix-cross-build job that would check it is the thing this PR adds. That job is the right place for that claim to live.

The reasoning about why the pointer is needed is still the reason, and it is now also the fix on main: signalling a process mutates it, and a value makes the compiler insert an automatic reference that it then rejects as deprecated. The comment above terminate_process already said so; the signature had drifted away from it.

build.vsh no longer collides with #256

Both this branch and #256 added a 'vinix': ['uptime'] entry to the per-platform exclusion map, which conflicted. Rather than have one delete the other at merge time, #256 now no longer touches vinix at all — its diff is only the Windows exclusion list, which is what that PR is about — and the entry plus its explanation stays here. The two merge in either order; I checked with git merge-tree, which is clean both ways.