Build fail on Windows with gcc ver. 0.3.30 about curl-rust

[alexcrichton]

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.

[LeMoussel]

I'm newbie in Rust. How can I get full error logs?

[alexcrichton]

Oh they should be printed to the console, but if they're not there then there's more hunting to do!

[alexcrichton]

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!

[LeMoussel]

Same problem

Downloading libz-sys v1.0.5
Downloading gcc v0.3.31
Compiling gcc v0.3.31
Compiling curl-sys v0.2.0
Compiling libz-sys v1.0.5
error: failed to run custom build command for curl-sys v0.2.0
Process didn't exit successfully: C:\Users\lemoussel\OneDrive\RUST Project\htmlparser\target\release\build\curl-sys-81c7fcebd44133fa\build-script-build (exit code: 101)

"cargo build --release" completed with code 101

[alexcrichton]

Hm it's surprising that nothing else is printed, what are the contents of: target/release/build/curl-sys-81c7fcebd44133fa/output?

Also, what version of Cargo are you using?

[LeMoussel]

C:\Users\lemoussel\OneDrive\RUST Project\htmlparser>rustc -vV
rustc 1.10.0 (cfcb716cf 2016-07-03)
binary: rustc
commit-hash: cfcb716cf0961a7e3a4eceac828d94805cf8140b
commit-date: 2016-07-03
host: x86_64-pc-windows-msvc
release: 1.10.0

C:\Users\lemoussel\OneDrive\RUST Project\htmlparser>cargo --version
cargo 0.11.0-nightly (259324c 2016-05-20)

I'm use Rust 1.10.0 Windows 64 bit (MSVC ABI)

Contents of: target/release/build/curl-sys-81c7fcebd44133fa/output.zip

[alexcrichton]

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?

[alexcrichton]

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...