Isuru Fernando
Isuru Fernando
You can't link two libraries with different ABI. you need the same ABI. For eg see https://github.com/riscv-collab/riscv-gnu-toolchain/issues/356
I don't think there's anything specific to RISCV you have to do. I think `LLC_HOST_CPU=generic-rv64` given is wrong. `generic-rv64` might mean soft-float ABI. You need a better architecture name to...
Can you try `EXTRA_HOST_LD_FLAGS="-target-abi=lp64"` as well?
And also `EXTRA_HOST_CLANG_FLAGS` and `EXTRA_HOST_AS_FLAGS`?
WIN64: OpenBLAS ctest with errors when linked against libopenblas.dll but works if build statically.
This is a limitation in windows. The tests rely on a test specific `xerbla` to be used to catch these illegal parameters given in tests. This works fine on Unix...
Is there a python function in conda or conda-build that we can use to verify that a version string is conda compliant?
Thanks @kalefranz, is there an equivalent in conda 4.3?
``` In [10]: conda.__version__ Out[10]: '4.3.34' In [11]: ms = MatchSpec(version='1.2.3') --------------------------------------------------------------------------- TypeError Traceback (most recent call last) in () ----> 1 ms = MatchSpec(version='1.2.3') TypeError: __new__() got an unexpected...
Looks like conda now allows `-`s in the version string as long as there is no `_`. conda-build chokes on this though. See https://github.com/conda-forge/conda-smithy/issues/779
Python 3.11 installation fails because there are no wheels and when building by source you need symengine and its dependencies installed already.