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.

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

Build failure on crates + master, compiler need mismatch #332

Closed
amyipdev opened this issue Mar 19, 2021 · 3 comments
Closed

Build failure on crates + master, compiler need mismatch #332

amyipdev opened this issue Mar 19, 2021 · 3 comments
Labels
pending release Issues that will be fixed by the next release

Comments

@amyipdev
Copy link

Context: gimli-rs/object#285

Object's compiler bug only occurs on the nightly version used to compile c2rust. C2Rust of course can't compile on stable due to an issue with the AST builder:

error[E0463]: can't find crate for `rustc`
 --> /home/amy/.cargo/registry/src/github.com-1ecc6299db9ec823/c2rust-ast-builder-0.15.0/src/lib.rs:2:1
  |
2 | extern crate rustc;
  | ^^^^^^^^^^^^^^^^^^^ can't find crate

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: could not compile `c2rust-ast-builder`
@thedataking
Copy link
Contributor

Please have a look at #323 for a possible way to compile object on the nightly version required by C2Rust.

milahu added a commit to milahu/c2rust that referenced this issue Dec 3, 2021
fix immunant#332 error: can't find crate for `rustc`
@milahu
Copy link
Contributor

milahu commented Dec 3, 2021

with rust-nightly-2019-12-05 and cargo build --locked i still get

   Compiling c2rust-ast-builder v0.15.0 (/build/source/c2rust-ast-builder)
error[E0463]: can't find crate for `rustc`

this is on nixos linux so this error probably appears only in clean environments

fixed in #354

milahu added a commit to milahu/c2rust that referenced this issue Dec 3, 2021
milahu added a commit to milahu/c2rust that referenced this issue Dec 3, 2021
@rinon rinon added the pending release Issues that will be fixed by the next release label May 10, 2022
@rinon
Copy link
Contributor

rinon commented May 12, 2022

Fixed in the v0.16.0 release

@rinon rinon closed this as completed May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending release Issues that will be fixed by the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants