shym

Spotted again in the [scheduled run](https://github.com/ocaml-multicore/multicoretests/actions/runs/13233110984/job/36933359317) on Cygwin **trunk** (with the relevant part of the timestamp): ``` 05:07:39 random seed: 262132514 05:07:39 generated error fail pass / total time test...

Spotted again in the [scheduled run](https://github.com/ocaml-multicore/multicoretests/actions/runs/14828712638/job/41625888541) on Cygwin 5.4 branch (with the relevant part of the timestamp): ``` 04:48:21 random seed: 476402853 04:48:21 generated error fail pass / total time...

I moved it accordingly (and rebased it). Is that a proper way to report the corresponding bug, by the way?

I added a grep that will hopefully work across platforms :crossed_fingers: But CI now fails on macos on a test this PR does not modify ?!?

Thank you @Alizter for your advice! I gave it some thoughts but I’m not sure what would be the best way to tackle this. The two possible solutions I’ve contemplated...

FYI, I’ve just tagged `setup-dune` [version 1.0.0](https://github.com/ocaml-dune/setup-dune/releases/tag/v1.0.0) (with tags `v1` and `v1.0.0`) in particular with the ability to use stable binary releases of Dune.

You can see: - the minimal [demo code](https://github.com/shym/unikraft-simple/tree/args), - and its [run log](https://github.com/shym/unikraft-simple/actions/runs/13049695786/job/36406997458), until it expires.

> Curious about the instruction to only use the wrapper script _after_ building the compiler. Because the build system of the compiler sets the flags correctly. Forcing the extra flags...

I expected so too but, at least on OpenBSD 7.3, `stdatomic.h` is in the Clang resources and I could compile the OCaml 5.2 runtime which needs this header with the...

On an OpenBSD 7.5, I see: ``` $ echo '#include ' > test.c $ cc -H -c test.c . /usr/lib/clang/16/include/stdatomic.h [...] ```