-
Notifications
You must be signed in to change notification settings - Fork 459
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
Errors aren't shown to user #87
Comments
Hm, sounds like something is afoot! I don't think this is an issue with the gcc crate itself, because all errors are indeed shown. If anything this sounds like a Cargo issue going on here. I'm worried that not even this I'm gonna close this as this shouldn't be an issue with gcc-rs, but does this reproduce for you locally? I'd be curious to debug further and see if this is a Cargo issue. |
None of that output was being written to the console, nor was it being written to the |
@skeleten, out of curiosity, what sort of environment were you running Cargo in? Was it a |
Also, I'm specifically curious whether rust-lang/cargo#2630 may have broken something here (that's the only relevant change I can think of). |
I was running it in a normal |
I'm unable to reproduce the issue. After fucking with my msvc installation to reproduce the same issues @skeleten was encountering, I get the output of
And my versions:
|
I uploaded the complete build log here: https://gist.github.com/skeleten/b93631a6ebbd36d5fe765bdd99662869 Anything else I could provide for this issue? Note that after the |
@skeleten could you try with Rust 1.10.0? |
Okay, this time I definitely have the same nightly that @skeleten used.
|
|
@skeleten it looks like you had to configure It also looks like stdout may almost just be getting dropped entirely, but it may be worth doing something like this:
I'm curious if you see "hello" from that build script? |
This is an issues with vcvars and older versions of rustc/gcc-rs where it picks the highest numbered folder as the ucrt candidate, even if there is no |
@alexcrichton I have VS 2015 Enterprise Installed - did not modify anything about my
|
I'm using |
@skeleten hm this all definitely sounds quite suspicious! Could I take a look at the build script you've written so far? |
@alexcrichton I'm trying to use it as a dependency of another dependency, so I haven't actually written any build script by myself. Edit 2: after some consulting in IRC, building
|
In this gist the "explicit panic" is from a
fail
helper method that prints out the message. As you can see however, the actual message isn't show to the user. This kinda makes it hard to know what the error was.The message should probably be printed to stderr, not stdout, anyway.
The text was updated successfully, but these errors were encountered: