Luca Barbato

We can double check, windows is not a platform I use.

Open an issue on cargo and link this one so once it is solved we won't forget about it :)

You are using those types as key part of your API, users cannot opt out and they have to ensure that they keep the two crates in sync in their...

``` export CHROME_PATH="/Applications/Chromium.app/Contents/MacOS/Chromium" ``` seems a satifying workaround, in case upstream is slow at addressing it. Thank you a lot for the quick reply!

if you use 1 slot and 2 threads does it still hang?

It needs a rebase.

The macos failing test makes me wonder if there isn't a valgrind.

What is the host system? those `export` feel wrong. we need to build the build_script as host, since you want to run it.

https://github.com/BtbN/FFmpeg-Builds/blob/master/scripts.d/50-rav1e.sh#L32 those are wrong you should remove them. You only need set the `linker`, since our assembler is nasm. Tell me if it works better for you :)

The problem is due our `build.rs` using libgit2 to extract some git information and apparently your image/linker has a faulty libz. Try to update your base image and the problem...