rust-lang / rust-lang/rustc_codegen_gcc
Build error: undefined symbol: gcc_jit_context_get_target_builtin_function
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 105
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 14
Description
Hi,
I have been trying following the instructions to build rustc_codegen_gcc with the README instructions and got the following error.
./build.sh --release
...
[BUILD] sysroot
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -Cpanic=abort -Csymbol-mangling-ver
sion=v0 -Cdebuginfo=2 -Clto=off -Zpanic-abort-tests -Zcodegen-backend=/home/lukyxu/repos/rust/rustc_codegen_gcc/targ
et/release/librustc_codegen_gcc.so --sysroot /home/lukyxu/repos/rust/rustc_codegen_gcc/build_sysroot/sysroot -Z forc
e-unstable-if-unmarked -Cpanic=abort --target x86_64-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-ty
pe dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit statu
s: 1)
--- stderr
error: couldn't load codegen backend "/home/lukyxu/repos/rust/rustc_codegen_gcc/target/release/librustc_codegen_gc
c.so": /home/lukyxu/repos/rust/rustc_codegen_gcc/target/release/librustc_codegen_gcc.so: undefined symbol: gcc_jit_c
ontext_get_target_builtin_function
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README build instructions and the failing ./build.sh --release command. Investigate why the built librustc_codegen_gcc.so cannot resolve gcc_jit_context_get_target_builtin_function, then rerun the build and sysroot compilation; done means rustc loads the backend without the undefined-symbol error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100