-
Notifications
You must be signed in to change notification settings - Fork 4
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
ld not found (strict_action_env) #57
Comments
Possibly related: bazelbuild/bazel#21334 |
A potential workaround for this stage is in .bazelrc:
|
I cannot reproduce this on my machine, but I see that the path to the linker ( I like your suggestion for adding an explicit cc_toolchain! Can you test building with that flag (whenever you have capacity)? |
Describe the bug
ld
cannot be found during build.To Reproduce
Expected behavior
It should build the go-server binary.
Environment
Suspicion
Inside the nix-shell, the linker is at
/nix/store/bgcaxhhxswzvmxjbbgvvaximm5hwghz1-binutils-2.41/bin/ld
. The dir of it is in thePATH
envvar. However, because of--incompatible_strict_action_env
is in the.bazelrc
file, PATH is not inherited, and the build fails. Note, gcc can be found (Probably it is discovered during local_config_cc_toolchain generation, that runs with the repo env, that inherits PATH regardless), but gcc can't find ld. Perhaps an explicit tc_toolchain should be set up?The text was updated successfully, but these errors were encountered: