-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Importing rustc_driver
interferes with rustc_codegen_llvm
items and leads to a linking error
#102065
Labels
A-linkage
Area: linking into static, shared libraries and binaries
C-bug
Category: This is a bug.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
Comments
The entire code is available here, Dockerfile included. |
I managed to minimize the code: #![feature(rustc_private)]
extern crate rustc_codegen_llvm;
extern crate rustc_driver;
fn main() {
unsafe {
rustc_codegen_llvm::llvm::LLVMRustContextCreate(true);
}
} |
hkmatsumoto
added
the
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
label
Sep 20, 2022
In
But the one linked into
I notice that the link line does not include |
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Nov 14, 2022
…imulacrum Add a few known-bug tests The labels of these tests should be changed from `S-bug-has-mcve` to `S-bug-has-test` once this is merged. cc: rust-lang#101518 rust-lang#99492 rust-lang#90950 rust-lang#89196 rust-lang#104034 rust-lang#101350 rust-lang#103705 rust-lang#103899 I couldn't reproduce the failures in rust-lang#101962 and rust-lang#100772 (so either these have started passing, or I didn't repro properly), so leaving those out for now. rust-lang#102065 was a bit more complicated, since it uses `rustc_private` and I didn't want to mess with that.
workingjubilee
added
A-linkage
Area: linking into static, shared libraries and binaries
S-bug-has-test
Status: This bug is tracked inside the repo by a `known-bug` test.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
and removed
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
S-bug-has-test
Status: This bug is tracked inside the repo by a `known-bug` test.
labels
Mar 4, 2023
hkmatsumoto
added a commit
to rustc-interactive/rust
that referenced
this issue
Mar 31, 2023
If `interactive` is set to true, codegen will special case that to get faster and for the resulting LLVM IR to be executable from external programs such as REPL. This commit also has the following changes: - Added LLVM JIT-related API. - Stopped distributing rustc crates as rmeta files. See added code comment and rust-lang#102065 for detailed info. - Some visibility changes on existing APIs so they could be used by external programs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-linkage
Area: linking into static, shared libraries and binaries
C-bug
Category: This is a bug.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
I tried this code, which builds and runs without problem:
However, after I make this change:
I expected to see this happen: The compiler builds without errors.
Instead, this happened:
cargo build
fails with the message shown in "Output" section below.Meta
rustc --version --verbose
:Output
The text was updated successfully, but these errors were encountered: