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.

Sign up for GitHub

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

Jump to bottom

cargo rustc -- -Z no-trans always fails #1675

Closed
reem opened this issue Jun 3, 2015 · 1 comment
Closed

cargo rustc -- -Z no-trans always fails #1675

reem opened this issue Jun 3, 2015 · 1 comment

Comments

@reem
Copy link

reem commented Jun 3, 2015

Compiling the crate itself will always fail with an error similar to (example from compiling void):

$ cargo rustc --verbose -- -Zno-trans
Compiling void v0.0.4 (file:///Users/reem/code/rust/rust-void)
     Running `rustc src/lib.rs --crate-name void --crate-type lib -g -Zno-trans --out-dir /Users/reem/code/rust/rust-void/target/debug --emit=dep-info,link -L dependency=/Users/reem/code/rust/rust-void/target/debug -L dependency=/Users/reem/code/rust/rust-void/target/debug/deps`
could not rename dep info: "/Users/reem/code/rust/rust-void/target/debug/void.d"

Caused by:
  No such file or directory (os error 2)
@reem
Copy link
Author

reem commented Jun 3, 2015

The error remains even after a cargo clean or a normal build.

alexcrichton added a commit to alexcrichton/cargo that referenced this issue Jun 10, 2015
@alexcrichton
Handle missing files after cargo rustc
8230f1f 
Some flags to the compiler could cause it to stop early or not emit some files
altogether (or perhaps emit files in different locations even). Currently cargo
expects a few outputs of the compiler after `cargo rustc` is run, but this
commit alters cargo to know that when `cargo rustc` is being run that the
outputs may not exist and that's ok.

Closes rust-lang#1675
@alexcrichton alexcrichton mentioned this issue Jun 10, 2015
Merged
bors added a commit that referenced this issue Jun 12, 2015
@bors
Auto merge of #1701 - alexcrichton:lenient-rustc-flags, r=brson
f98100f 
Some flags to the compiler could cause it to stop early or not emit some files
altogether (or perhaps emit files in different locations even). Currently cargo
expects a few outputs of the compiler after `cargo rustc` is run, but this
commit alters cargo to know that when `cargo rustc` is being run that the
outputs may not exist and that's ok.

Closes #1675
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@reem