-   Notifications  You must be signed in to change notification settings 
- Fork 13.9k
Open
Labels
C-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)needs-triageThis issue may need triage. Remove it if it has been sufficiently triaged.This issue may need triage. Remove it if it has been sufficiently triaged.
Description
Hi.
I tried setting LD_LIBRARY_PATH to use a different libgccjit, but it doesn't seem to work anymore.
I expected that bootstrap would pick the libgccjit.so file from LD_LIBRARY_PATH.
Instead, bootstrap kept its version from build/x86_64-unknown-linux-gnu/stage2/lib.
Meta
I tried on commit 8aab621.
Some more details.
I expect that some people would want to do something similar with LLVM.
 What do people do to test a different LLVM version when hacking on rustc? Does it work by just setting LD_LIBRARY_PATH?
cc @Kobzol
Thanks.
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)needs-triageThis issue may need triage. Remove it if it has been sufficiently triaged.This issue may need triage. Remove it if it has been sufficiently triaged.