Skip to content

Better diagnostics for error: can't find crate for ... [E0463] #32663

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

Open
Zoxc opened this issue Apr 1, 2016 · 3 comments
Open

Better diagnostics for error: can't find crate for ... [E0463] #32663

Zoxc opened this issue Apr 1, 2016 · 3 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@Zoxc
Copy link
Contributor

Zoxc commented Apr 1, 2016

It would be nice if rustc would print the search directory for a crate and rejected crates (with matching names) in those directories when it cannot find the crate.

@Zoxc
Copy link
Contributor Author

Zoxc commented Apr 1, 2016

The debug! macros here should be changed to info! so rustc doesn't have to be recompiled for detailed information.

@apasel422 apasel422 added the A-diagnostics Area: Messages for errors, warnings, and lints label Jun 17, 2016
@steveklabnik steveklabnik added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Mar 9, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-enhancement Category: An issue proposing an enhancement or a PR with one. label Jul 24, 2017
@jwarley
Copy link

jwarley commented Feb 5, 2018

Related: I got this error as the result of trying to compile from a corrupted installation (rustup ran out of space but didn't raise any errors). In particular, rustc reported can't find crate for `core` which `std` depends on. In this case, ~/rustup/toolchains/[target]/lib/rustlib/[target]/lib/libcore*.rlib was present, but its size was zero (so the logical debugging strategy of checking the file paths and sysroot didn't reveal the problem). Running with debugging reported "File too small to be an archive" for libcore. It might be nice to report "can't find" and "found but obviously corrupted" as different errors.

@steveklabnik
Copy link
Member

Triage: not aware of any better diagnostic here yet!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants