-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileNotFound when compiling macos #9431
Comments
Also seeing this issue on MacOS. Unfortunately it consistently fails in my experience. The project just will not build when targeting MacOS with Zig. I assume this is because I'm building a large repository with lots of C, rather than just a single library. Additionally, the proposed workaround in bazel-zig-cc does not work. With flock
Without flock
It might be important to note that this build works when targeting Linux with Zig (without flock!), and works with the local cc toolchain on MacOS. |
Strange: https://git.sr.ht/~motiejus/bazel-zig-cc/tree/main/item/.envrc Though I didn't add
This is not OSX-specific. I keep hitting into this at least once a week on Linux, but OSX has been the easiest to reproduce. I can reliably reproduce it in our CI environment though (worked 100% of the time so far), but we run a lot of tests there on many different hosts/shards. I am 99.9% sure this is a duplicate to #9439, thus will close now. @andrewrk thanks for pointing to the other ones. |
I get a
FileNotFound
error when compiling a Go project using Bazel on MacOS. Specifically Bazel is interesting, because it invokeszig c++
in parallel.Full execution output when compiling this program:
Execution output:
To reproduce (on macos x86_64, requires direnv to be installed):
Note that it fails only the first time; subsequent executions compile the file successfully, no matter which caches I try to prune (strange, advice appreciated).
I have the full build directory with the artifacts from this build, and can upload any requested files for further inspection.
The text was updated successfully, but these errors were encountered: