Stan Seibert

Oh! I think that would require us to build LLVM with the RISC-V target enabled on x86 and link to that when building the llvmlite wheels. I'm not sure what...

I did a quick test, and adding the RISCV target to Linux x86_64 seems to add 6 MB to the LLVM compressed package size (which llvmlite end users do not...

FYI: I have a PR now to add RISC-V as a target on all platforms. If accepted, it should roll out with the next Numba/llvmlite release before the end of...

@stuartarchibald has suggested just turning on all the default LLVM targets, which are (for LLVM 11): `AArch64, AMDGPU, ARM, BPF, Hexagon, Mips, MSP430, NVPTX, PowerPC, Sparc, SystemZ, X86, XCore`. We...

OK, turning on all those targets adds 30% to the size of both llvmdev and llvmlite. In the case of statically linked llvmlite, it grows from 22MB to 29MB. That...

OK, I've upgraded #788 to add in every default target in LLVM 11 + RISC-V.

What would the equivalent of pycc be for llvmlite? pycc (or rather, the [API that superseded it](http://numba.pydata.org/numba-doc/0.39.0/user/pycc.html)) is for ahead of time compilation of Python functions. The frontend for translating...

We don't have any documentation, but llvmlite still has an `llvmpy` submodule which provides some backward compatible interfaces that were used to ease the Numba transition several years ago: https://github.com/numba/llvmlite/tree/master/llvmlite/llvmpy...

(Note that the llvmpy -> llvmlite transition was several years ago, so these backward compatibility interfaces may be removed in a future release.)

It isn't totally clear from this error what all is going on. One of the errors indicates that pip is trying to build llvmlite from source code, which is challenging...