Fabian Meumertzheim
Fabian Meumertzheim
Hmm, this is certainly not the desired behavior. Could you provide steps to reproduce this as well as the error you are seeing?
Is there a portable shebang that would work? `/usr/bin/env bash` perhaps? Happy to review a PR.
Could you try to set `--shell_executable` to some other path?
Wouldn't we still have to find and invoke the shell in that case? Could you instead send a change to rules_shell that detects the shell binary on your system?
There's a proposal for doing this in Bazel, but it's tricky to add a toolchain dependency only if run_shell is used. I think that run_shell should become a Starlark wrapper...
I agree that we need something like this patch, but I would prefer one that disables the `pic` feature instead of manually stripping certain hardcodes flags. This may require inlining...
I think I'm a bit confused by the todo. If I understand the logic you linked correctly, it applies to cases where the linker by default (that is, without any...
The problem is that Bazel doesn't know which files changed. I guess we could offer a flag that you could supply a list of files to and then we would...
There have been quite a lot of changes to nogo since 0.46.0. Could you check whether 0.50.1 fixes this? If not, a PR would be very welcome.
The metadata files are mutable, so we could fix them. Is there a way to automate trivial schema fixes like this?