Elliot Saba

> The only problem is that BinaryProvider expects the archive to have a specific structure (e.g., no top directory) Note that this can be worked around by setting up the...

Would it be helpful to try building ROOT against the _exact_ version of LLVM that Julia uses? Julia is also quite opinionated about the LLVM it uses, as I'm sure...

We can export an LBT API that allows manually setting function pointers; so if you can get a function pointer to a Julia function, we can have LBT forward to...

If it's an actual shared library, it's probably not so bad; you can do something like: ``` # Open BLASFEO blasfeo_handle = dlopen(blasfeo_path, RTLD_LOCAL) # Configure BLASFEO as ILP64 or...

I've switched to buildkite, which is working.

This is happening because [we forward-declare functions as a `const void *`](https://github.com/staticfloat/libblastrampoline/blob/491f33022e002fa9c60116da64af5b00efcae5d2/src/libblastrampoline_f2cdata.h#L25), and that's fine because the ABI interface for a `void *` and a function are the same once...

You need to load Apple Accelerate first: ## On Apple Silicon (which has no complex return style problems) ``` julia> using LinearAlgebra, LAPACK_jll BLAS.lbt_forward("/System/Library/Frameworks/Accelerate.framework/Accelerate"; verbose=true, clear=true) BLAS.lbt_forward(LAPACK_jll.liblapack_path; verbose=true) Generating forwards...

> Is it a problem that the different libraries (BLAS From Accelerate and LAPACK from Ygg) have different fortran calling conventions and different complex return style? I don't think it...

Hmmm, I think I agree! I would be happy to accept a PR making this change, to force MKL to use `MKL_Domain_Set_Num_Threads` instead of `MKL_Set_Num_Threads`.

Yes, we need to essentially special-case this.