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

Non-UTF-8 output on localized MSVC #3012

Closed
Boddlnagg opened this issue Aug 17, 2016 · 5 comments
Closed

Non-UTF-8 output on localized MSVC #3012

Boddlnagg opened this issue Aug 17, 2016 · 5 comments

Comments

@Boddlnagg
Copy link
Contributor

Boddlnagg commented Aug 17, 2016

This might be related to the comments in #2560, but I'm not sure: A localized (e.g. German) MSVC can produce non-UTF-8 output, which can become almost unreadable in the way it's currently forwarded to the user.

This can be seen in an (otherwise unrelated) issue comment: rust-lang/cc-rs#87 (comment)
Note especially this line:

note: Non-UTF-8 output: LINK : fatal error LNK1104: Datei \"ucrt.lib\" kann nicht ge\xf6ffnet werden.\r\n

That output might be a lot longer for multiple LNK errors (one line per error, but the lines are not properly separated in the output, because they are converted to \r\n) and become really hard to read.
If possible, the output should be converted to Unicode in this case.

@alexcrichton
Copy link
Member

Interesting! Are you seeing these messages as part of a standard cargo build?

@Boddlnagg
Copy link
Contributor Author

No, I'm modifying linker arguments with cargo rustc ... -Clink-args=..., so the actual linker errors are totally my fault, but I would like to read them to see what I'm doing wrong 😉

@alexcrichton
Copy link
Member

Oh actually this output is coming from the compiler, not from Cargo. Can you open a bug over there instead?

@Boddlnagg
Copy link
Contributor Author

Done.

@alexcrichton
Copy link
Member

Thanks!

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