This may break RISC-V platform. This commit may be the reason https://boringssl.googlesource.com/boringssl/+/1967621cc9498a4d775a8a9eaabbcb7a52be8316

Is it possible to port (or even better upstream) the cmake files?

Cc @SpriteOvO

For RISC-V, looks like it just needs a simple patch, I will try to upstream it to boringssl in the next few days.

I have compiled the latest boringssl without patching on RISC-V. That commit did not break RISC-V since it just added code files for specific arch and RISC-V doesn't need specific files.

However, the latest boringssl triggers a strange error that looks like a bug from STL or gcc, I'm trying to investigate it, it doesn't relate to android-tools or boringssl I guess, so this PR can be merged safely, and no porting is needed :)

Thank you for the confirmation @SpriteOvO

Thank you for the PR! Should I tag a new release or does this warrant further testing? (: