[bazel] fix lld system requirement
#12448
Comments
18 tasks
timothytrippel
added
Priority:P1
|
Deferring post M2 as there is a workaround. |
tjaychen
pushed a commit
to tjaychen/opentitan
that referenced
this issue
Sep 1, 2022
supplements lowRISC#12448 Signed-off-by: Timothy Chen <[email protected]>
tjaychen
pushed a commit
to tjaychen/opentitan
that referenced
this issue
Sep 1, 2022
supplements lowRISC#12448 Signed-off-by: Timothy Chen <[email protected]>
tjaychen
pushed a commit
that referenced
this issue
Sep 1, 2022
supplements #12448 Signed-off-by: Timothy Chen <[email protected]>
|
In my case on CentOS, this required symbolically linking |
|
@dbeitel-opentitan Are you still suffering from this issue in your build environment? Could you give some details about your environment (OS, version, packages installed) so that I might try to duplicate the problem? |
|
Mmm, I don't remember this issue. I don't think I ran into this problem (At least I don't remember it). |
|
Yes still facing this issue
|
timothytrippel
added a commit
to timothytrippel/rules_rust
that referenced
this issue
Sep 13, 2023
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]>
|
Status Update: I have identified the source (but not root cause) of the issue and drafted document to describe to one might observe the issue: https://docs.google.com/document/d/1GWEHfkZZI_Fz8JMytCY7cPozi5j9xt1SiWmq-Zf0Mak/edit?usp=sharing The document also contains pointers to a potential patch to rules_rust that we could merge into the lowRISC fork. Still working with Todd to resolve this. |
timothytrippel
added a commit
to timothytrippel/rules_rust
that referenced
this issue
Sep 14, 2023
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]>
|
lowRISC/rules_rust#4 should patch our fork of rules_rust to enable a workaround |
timothytrippel
added a commit
to lowRISC/rules_rust
that referenced
this issue
Sep 16, 2023
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
added a commit
to timothytrippel/opentitan
that referenced
this issue
Sep 16, 2023
This updates rules_rust to make use of a new patch that was added in the lowRISC fork of rules_rust that enables a workaround for lowRISC#12448. The workaround provides a command line build flag `--@rules_rust//:extra_rustc_toolchain_dirs=/path/to/somewhere/else` that you can add to your `.bazelrc` file to specify a different location on your system where host toolchain tools may be found. Signed-off-by: Tim Trippel <[email protected]>
timothytrippel
added a commit
to timothytrippel/opentitan
that referenced
this issue
Sep 18, 2023
This updates rules_rust to make use of a new patch that was added in the lowRISC fork of rules_rust that enables a workaround for lowRISC#12448. The workaround provides a command line build flag `--@rules_rust//:extra_rustc_toolchain_dirs=/path/to/somewhere/else` that you can add to your `.bazelrc` file to specify a different location on your system where host toolchain tools may be found. Signed-off-by: Tim Trippel <[email protected]>
timothytrippel
added a commit
that referenced
this issue
Sep 18, 2023
This updates rules_rust to make use of a new patch that was added in the lowRISC fork of rules_rust that enables a workaround for #12448. The workaround provides a command line build flag `--@rules_rust//:extra_rustc_toolchain_dirs=/path/to/somewhere/else` that you can add to your `.bazelrc` file to specify a different location on your system where host toolchain tools may be found. Signed-off-by: Tim Trippel <[email protected]>
h-filali
pushed a commit
to h-filali/opentitan
that referenced
this issue
Sep 20, 2023
This updates rules_rust to make use of a new patch that was added in the lowRISC fork of rules_rust that enables a workaround for lowRISC#12448. The workaround provides a command line build flag `--@rules_rust//:extra_rustc_toolchain_dirs=/path/to/somewhere/else` that you can add to your `.bazelrc` file to specify a different location on your system where host toolchain tools may be found. Signed-off-by: Tim Trippel <[email protected]>
nbdd0121
pushed a commit
to nbdd0121/rules_rust
that referenced
this issue
Nov 14, 2023
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]>
nbdd0121
pushed a commit
to nbdd0121/rules_rust
that referenced
this issue
Nov 15, 2023
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since #12263, there is a new system requirement (the LLVM linker
lld) needed to prevent the build from erroring out with:Temporary solution:
The temporary solution is to simply:
lldwith:sudo apt install lldlldto the relevant*-requirements.txtfilesLong-term solution:
Figure out why bazel is attempting to use
gccwithlldto build some rust crates.Hints:
The text was updated successfully, but these errors were encountered: