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) #1905

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

Comments

@LigH-de
Copy link
Contributor

LigH-de commented Jan 25, 2021

cargo-c issue 159 - suggested workaround: cargo install cargo-c --locked

ab-suite.rust.install.log


PS: cargo issue 9101 - may get fixed upstream soonish

@HunterAP23
Copy link

HunterAP23 commented Jan 25, 2021

Not sure that posting an issue due to an external dependency of a dependency is broken, but sure.
I tried running cargo install cargo-c --locked in the mintty environment but a different error came up.

You can still build FFmpeg but you need to explicitly disable the building aom, rav1e1, dav1d, and libavif=2 in build/media-autobuild_suite.ini and build/ffmpeg_options.txt. The names are different in in the build/ffmpeg_options.txt file, so here's how they map out:

library media-autobuild_suite.ini ffmpeg_options.txt
aom set aom=2 change --enable-libaom to --disable-libaom
dav1d set dav1d=2 change --enable-libdav1d to --disable-libdav1d
rav1e set rav1e=2 change --enable-librav1e to --disable-librav1e
avif set libavif=2 No changes needed

Then retry the build and cargo-c won't be a problem since it's only used to build the above libraries.

@LigH-de
Copy link
Contributor Author

LigH-de commented Jan 26, 2021

I mainly posted it to report that I already investigated a bit about the reason, and it is not the fault of the suite... so the main solution (if you want to build anything that depends on rust) is "patience".

@LigH-de
Copy link
Contributor Author

LigH-de commented Jan 28, 2021

This "different error" is an interesting one... essentially:

  = note: ld: cannot find -lntdll

cargo-c.install-locked.log

Maybe it requires custom directory variables.

@LigH-de
Copy link
Contributor Author

LigH-de commented Feb 4, 2021

Solved.

@LigH-de LigH-de closed this as completed Feb 4, 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

2 participants