Thomas
Thomas
I imagine the original issue for this is probably resolved. I haven't seen it in a long time, but also have been using a caching strategy where each invocation of...
Hmm, I'm not so sure that conclusion is correct. The `ZIG_LOCAL_CACHE_DIR` and `ZIG_GLOBAL_CACHE_DIR` environment variables were and always have been identical. https://git.sr.ht/~motiejus/bazel-zig-cc/tree/361fc42b2e1282ed078bf9c1ad281642e19858d4/item/toolchain/defs.bzl#L191
Looks like this issue still shows up occasionally. Version `0.10.0-dev.1393+291f5055f`. Example: ``` ld.lld: error: cannot open /var/folders/3k/z0djtwqd4s5_xrwz0nlgfx700000gp/T//bazel-zig-cc/o/577b5020915dd149714a9b44041a9be8/Scrt1.o: No such file or directory ld.lld: error: cannot open /var/folders/3k/z0djtwqd4s5_xrwz0nlgfx700000gp/T//bazel-zig-cc/o/ee268b08503a370b073e628082bd0a9d/crti.o: No such file...
Looks okay, we'll need to understand why CI isn't happy and then we can merge.
Ran into this today, really confusing. [capnproto](https://github.com/capnproto/capnproto) uses the 'c++' file extension, which is looks like zig doesn't support. https://github.com/ziglang/zig/blob/1fee9eac8bb5d2e3e78c098b9cebe2cda332e7cf/src/Compilation.zig#L3938 Could support be added for common c++ extensions?
Looks like there has been some groundwork for this here: https://github.com/ziglang/zig/blob/1fee9eac8bb5d2e3e78c098b9cebe2cda332e7cf/src/Compilation.zig#L4349, but other code like the previously linked would need to use this. (and add '.c++').
Bazel has a nice list of extensions: https://docs.bazel.build/versions/main/be/c-cpp.html#cc_library > Permitted srcs file types: > > C and C++ source files: .c, .cc, .cpp, .cxx, .c++, .C > C and C++...
> Fix for `v1.10.0`: > > ``` > # See https://github.com/open-telemetry/opentelemetry-go-contrib/issues/872 > go_repository( > name = "io_opentelemetry_go_otel", > build_directives = [ > "gazelle:go_visibility @io_opentelemetry_go_otel_metric//:__subpackages__", > ], # keep > build_file_proto_mode...
Saw this again for `io_k8s_sigs_kustomize_api/internal/git/BUILD.bazel:3:11`. Again apologies for not being able to provide a good reproduction. It's intermittent and confusing. ``` compilepkg: panic: runtime error: index out of range [7]...
Hi @dominikh. I'm working to find a way to reproduce this, but so far have not. This is an issue as we see it happen transiently, but have no idea...