-
Notifications
You must be signed in to change notification settings - Fork 234
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
Build fail on Windows with gcc ver. 0.3.30 #116
Comments
Thanks! Could you also gist the full error logs of what happened as well? It's failing locally for me as well and I'm investigating, but just want to make sure we're hitting the same error. |
I'm newbie in Rust. How can I get full error logs? |
Oh they should be printed to the console, but if they're not there then there's more hunting to do! |
Ok, pushed a new build of gcc-rs to 0.3.31 which I think should fix this. If you still have problems though let me know! |
Same problem
|
Hm it's surprising that nothing else is printed, what are the contents of: Also, what version of Cargo are you using? |
I'm use Rust 1.10.0 Windows 64 bit (MSVC ABI) Contents of: target/release/build/curl-sys-81c7fcebd44133fa/output.zip |
Hm I wonder if that output file is stale, it's showing success but Cargo thinks the build script is failing! Could you try removing it, re-running, and see if it's recreated? |
So another thing I'm worried about is that rust-lang/cargo#2630 changed how Cargo reads stdout/stderr of build scripts, and something about that may be wrong which hides the stdout/stderr of build scripts by accident. It seems that all the diagnostics printed out by the build script are getting shoved under the rug somewhere... |
crate gcc are updated to 0.3.30 on Jul 13, 2016.
When I compil on Windows 10, I got this error :
I update to gcc Ver. 0.3.28 in cargo.toml like this :
It's work fine.
The text was updated successfully, but these errors were encountered: