Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add build setting to enable specifying other tool locations #4

Merged
merged 1 commit into from
Sep 16, 2023
Merged

Add build setting to enable specifying other tool locations #4

merged 1 commit into from
Sep 16, 2023

Commits on Sep 14, 2023

  1. Add build setting to enable specifying other tool locations 

    On some systems, the CC toolchain discovered by bazel uses a different
path for the linker than where the linker (that is specified by the
`-fuse-ld=` flag) actually lives on the system.

The issue stems from rules_rust deciding to pass `-fuse-ld=lld` a link arg,
rather than just using what was detected by the CC toolchain. This results
in the linker not being found, as reported by
lowRISC/opentitan#12448

This is a workaround that enables telling rules_rust where other linker
directories might be on your system. It is used by passing
`--@rules_rust//:extra_rustc_toolchain_dirs=/path/to/somewhere/else` to
`bazel ...` invocations.

Signed-off-by: Tim Trippel <[email protected]>
    @timothytrippel
    timothytrippel committed Sep 14, 2023
    Configuration menu
    Copy the full SHA
    d145d71 View commit details
    Browse the repository at this point in the history