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

cargo-c v0.7.1+cargo-0.49: compiling fails (de.rs:530:63 - type annotations needed) #159

Closed
LigH-de opened this issue Jan 25, 2021 · 3 comments

Comments

@LigH-de
Copy link

LigH-de commented Jan 25, 2021

Trying to compile cargo-c in media-autobuild suite (MSYS2/MinGW) as prerequisite of rav1e encoder:

error[E0283]: type annotations needed
   --> E:/MABS/msys64/opt/cargo\registry\src\github.com-1285ae84e5963aae\cargo-0.49.0\src/cargo\util\config\de.rs:530:63
    |
530 |                 seed.deserialize(Tuple2Deserializer(1i32, env.as_ref()))
    |                                                           ----^^^^^^--
    |                                                           |   |
    |                                                           |   cannot infer type for type parameter `T` declared on the trait `AsRef`
    |                                                           this method call resolves to `&T`
    |
    = note: cannot satisfy `std::string::String: AsRef<_>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0283`.
error: could not compile `cargo`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo-c v0.7.1+cargo-0.49 (E:\MABS\build\cargo-c-git)`, intermediate artifacts can be found at `E:\MABS\build\cargo-c-git\target`

ab-suite.rust.install.log

@dracupid
Copy link

dracupid commented Jan 25, 2021

Same problem, it seems that a dependency of cargo has updated with incompatible API change.
Try cargo install cargo-c --locked.

Update: Found upstream issue rust-lang/cargo#9101

@lu-zero
Copy link
Owner

lu-zero commented Feb 15, 2021

v0.7.2 should had addressed that. Is it still a problem?

@LigH-de
Copy link
Author

LigH-de commented Feb 15, 2021

Uh, yes, I closed the upstream issue but forgot this.

@LigH-de LigH-de closed this as completed Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants