Brian Smith

Isn't the problem that you have musl-gcc installed but you don't have a musl toolchain (with musl headers) installed?

> right shift count >= width of type This indicates to me that the musl headers you are using are 64 bit but the compiler is compiling in 32-bit mode.

What you're doing probably works with clang but not GCC. See below: ``` if (target.arch == "wasm32" && target.os == "unknown") || (target.os == "linux" && is_musl && target.arch !=...

@indygreg Did you get this working? Is this still an issue for you?

> It's no surprise that a 32bit uint64_t breaks things. AFAICT, when this happens, this means that the headers are mismatched to what the compiler expects. I have found that...

I have never tried to cross compile from macOS to another OS. However, I suggest you look at how we compile to -musl targets in CI using clang, and then...

> * arm-unknown-linux-gnueabihf > * arm-unknown-linux-musleabi > * armv7-unknown-linux-gnueabihf > * armv7-unknown-linux-musleabihf The *ring* CI/CD does build for some of those platforms, and shows how to install the tools to...

After I address #1473, it should be pretty easy to extend that work so that we don't need a C toolchain for cross-compiling to Linux.

I updated the description to indicate the intended scope: Add support for generating PKCS#1 SHA-1 signatures, only. I'm not intending to add support for PSS or OAEP support using SHA-1...

In order to support users who do want to enforce that 65537 is the minimum, we won't change the default behavior. Instead I propose we provide an alternate for each...