Rust update causing cargo error

help
1

Hello

I have updated to the recent rust version (1.72.0) on Windows machine. Since then cargo got messed up in my project, getting the following error:

** process didn't exit successfully: rustc -vV (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND)**

The functional previous version is : 1.71.1

Any hint to address it ?

2

did it happen for a specific project, or it happens for all projects? did you try cargo clean and then rebuild the project?

3

Never seen that before. My first guess would be that rustc is somehow unable to find one of the .dlls it needs... but I've never seen anyone with that issue.

How did you install Rust? Are you using rustup, an installer, or just unpacking an archive somewhere? Did you update it the same way, or did you change to a different method? Also, is this for cargo build, or is it some other command?

Edit: Also, do you remember what the previous version that did work was?

1 Like
4

Even cargo clean fails .....

cargo clean
error: process didn't exit successfully: rustc -vV (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND)

Here goes the snippet of the cargo.toml file:

.......................
.......................

[dependencies]

assert_approx_eq = "1.1.0"

rand = "0.8.5"

image = "0.24.5"

rayon = "1.7.0"

indicatif = { version = "0.17.3", features = ["rayon"] }

glam = "0.24.0"

[profile.release]

panic = 'abort'

5

just rolled back to the previous version "1.71.1" with the following command :

rustup install 1.71.1
rustup default 1.71.1

And cargo clean && cargo build is working fine.

Something is yet to be fixed in 1.72, I guess.

6

Out of curiosity, are you using the msvc or gnu variant?

7

msvc and for reference using the following link for installation:

8

Very bizarre. I just updated my stable-x86_64-pc-windows-msvc variant to 1.72 and can build fine.

9

Can you try removing 1.72 and re-installing it?

I have a very vague recollection from years ago of a rustup install that failed part way through, leaving a corrupt installation that I had to reinstall to get it working. If it never got around to installing one of the compiler libraries, that might explain it.

Also check that you have free space on your primary drive. My 1.68.2 toolchain takes ~1.5GB, so as long as you have a few GB free you should be okay.

1 Like
10

re-installed rust 1.72 with rustup and now encountering the following problem:

cargo clean && cargo build
Updating crates.io index
warning: spurious network error (3 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.)
warning: spurious network error (2 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.)
warning: spurious network error (1 tries remaining): [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.)
error: failed to get assert_approx_eq as a dependency of package

I guess we are supposed to get this error if the computer is behind a corporate firewall

11

Well, at least it's a different problem now. Progress! :tada:

I'm afraid I can't help you a firewall, though.

12

Eventually re-installing rust 1.72 instead of updating from 1.71.1 worked, had to reconfigure the proxy setup though with the following reference:

13

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.