Carlo Cabrera

Resolved by patching out the check. Debian doesn't even force usage of their own Boost for this, so I'm guessing that that's not a venture worth pursuing. In any case,...

Maybe, but I'm pretty sure this is Homebrew-specific. The check is almost definitely needed if you're building from source without using `brew`, which is why the first fix I attempted...

Did a fast-forward merge to preserve the commit hash.

As seen in Homebrew/homebrew-core#95485, this can seemingly be fixed by installing Homebrew `curl` and then passing the equivalent of `--search-prefix "$(brew --prefix curl)"` to `zig build`. However, this isn't really...

Yes, waiting for the release of 0.10.0 sounds like a much better idea. Thanks!

Incidentally, this is the same error as in #8999.

Thanks for having a look. Do you have both the CLT and Xcode.app installed? If you have the CLT installed, can you try doing some combination of ``` export SDKROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk...

Based on CI at Homebrew/homebrew-core#91763, it seems that it's the `CPATH` setting that's the culprit. My guess is that it ends up mixing headers from Xcode and the CLT and...

> It seems like it needs some macOS SDK?! ([cross-rs/cross#508](https://github.com/cross-rs/cross/issues/508)) The macOS SDK is installed on GitHub Actions macOS runners. (You actually probably need it to use Rust at all...

> > 1. Use a `portable-curl` similar to `portable-ruby` to avoid the need for an outside `curl`. It would be bult in its own repo modeled after `portable-ruby` and would...