1.0.85 on FreeBSD breaks with assertion failure "stderr should have no flags set"

[rtyler]

  running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-2" "-fno-omit-frame-pointer" "-m64" "--target=x86_64-unknown-freebsd" "-I" "zstd/lib/" "-I" "zstd/lib/common" "-fvisibility=hidden" "-ffunction-sections" "-fdata-sections" "-fmerge-all-constants" "-DZSTD_LIB_DEPRECATED=0" "-DXXH_PRIVATE_API=" "-DZSTDLIB_VISIBILITY=" "-DZSTDERRORLIB_VISIBILITY=" "-o" "/home/tyler/zofast/arrow-rs/target/debug/build/zstd-sys-275131524626fd8a/out/8957a4c8b028b07b-debug.o" "-c" "zstd/lib/common/debug.c"

  --- stderr
  thread 'main' panicked at /home/tyler/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cc-1.0.85/src/parallel/stderr.rs:17:9:
  assertion `left == right` failed: stderr should have no flags set
    left: 2
   right: 0
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I remember running into some issues with 1.0.84 which I know y'all ended up yanking, hit this on a fresh machine shortly after the 1.0.85 release Sorry to be such a buzzkill 😦

Will try to see what I can learn about the failure on a FreeBSD host. I wasn't able to reproduce it on x86_64-unknown-linux-gnu however

[NobodyXu]

cc @dpaoliello Seems like my assumption is wrong

[NobodyXu]

@rtyler Thanks for reporting, I will try to get it fixed ASAP and push a new release.

[rtyler]

@NobodyXu I'm in a slightly different timezone, but if you have commits in main I can take them for a spin