Fabian Meumertzheim
Fabian Meumertzheim
@linzhp I remember having seen this before, do you know how it could be solved?
I suspect that this can be fixed by manually specifying the gazelle directives that are automatically added with Bzlmod: https://github.com/bazelbuild/bazel-gazelle/blob/master/internal/bzlmod/default_gazelle_overrides.bzl Could you try that?
@popovicu Please let me know if this doesn't work for you and we can reopen.
That should work: The default locale of a C program is `C`, but that call to `setlocale` sets it to whatever the typical environment variables say.
Ah, nvm, forcing the C locale could be a problem if it ends up disallowing UTF-8 characters in filenames. In that case forcing `LC_ALL=C.UTF-8` in Linux or `LC_ALL=en_US.UTF-8` is probably...
CC @JamyDev
Are you also seeing these warnings with a non-Bazel Go build? It would be very helpful to see and compare the exact command lines the Bazel build and the Go...
You could override Go rules with `local_repository` or `local_path_override` and flip this flag in code: https://github.com/bazelbuild/rules_go/blob/6f206adcc9c2527a411a002669db1b7efafbeae8/go/tools/builders/env.go#L76 Together with `--subcommands`, this should allow you to see all compilation commands, including compiler...
Having the output base deleted sounds like a rather crude form of cleanup. For users that don't use a disk or remote cache, having their output base deleted on reboot...