bzip2-sys build fails on Windows when its path contains non-latin characters about bzip2-rs HOT 6 OPEN

This is quite odd... The bug is probably with gcc-rs of some form rather than this crate itself, but regardless it shouldn't be happening! I haven't been able to reproduce locally yet, unfortunately, however. Do you know of a way I could do so?

from bzip2-rs.

Did I understand you right, you tried non-latin characters in path and it didn't reproduce?
Anyway, this is not that critical, because I know a workaround and have already applied it.
The most unpleasant thing is that I don't have an idea how to debug this sort of bugs. AFAIK cargo runs the executable compiled from build.rs with tons of environment variables, and I have to know them all to catch it.

from bzip2-rs.

Hm yeah I'm not 100% sure if I did the right thing or not, but I ctrl-c + ctrl-v'd the directory name from above (Александр) into a terminal and then ran cargo build inside of that with a checkout of this repo.

Perhaps you could provide a program which when run exhibits this behavior? (e.g. programatically creates a directory with an offending character)

from bzip2-rs.

Seems you're doing right things.
I tried the following: I patched gcc-rs so it dumps everything from the build script into a file and reproduced the bug. Here is the result: https://www.dropbox.com/s/9y6rmt7mqj1sbtk/build.txt?dl=1

from bzip2-rs.

Hm it looks like that file is valid UTF-8, so it may not be precisely what Cargo is choking on. Is there a script that I could run to reproduce this?

from bzip2-rs.

I'm working on it and I'll provide it as soon as it's ready and reproducing consistently.

from bzip2-rs.