-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add as_executable to CcToolchainInfo #10344
Comments
cc @oquenchil |
Also hitting this when trying to do remote builds. |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
bump |
Description of the feature request:
Like we have an
ld_executable
and anar_executable
on the CcToolchainInfo API, add anas_executable
, which gives a string to the assembler executable.Feature requests: what underlying problem are you trying to solve with this feature?
When calling the graalvm native-image executable, that executable does, in turn, call the compiler. The path to the compiler can be specified with an option. However, gcc then tries to call
ld
(which is fine because it is already present in the toolchain), followed byas
, which is not exposed in the toolchain API.Relevant issue here.
What operating system are you running Bazel on?
The graal rules support mac OS and linux.
Have you found anything relevant by searching the web?
This issue asks for the same thing on the legacy api. However, it's not clear why it was closed when the new API was introduced, since the new API seemingly also does not have it.
#5494
The text was updated successfully, but these errors were encountered: