Add requisite libraries for ArrayFire #135
Conversation
|
can't the package be made to handle installation automatically? |
|
You need a login and a password to download the binary. I'm pulling from their Jenkins CI with persmission. |
| @@ -89,6 +89,13 @@ export PYTHON="" | |||
| sudo apt-get install wamerican | |||
| # Need xmllint (and others?) for XMLDict.jl | |||
| sudo apt-get install libxml2-utils | |||
| # ArrayFire | |||
| # ArrayFire | |||
|
ah, ok. why are they using atlas? |
|
It is listed as a pre-requisite in their docs. I think this is because it doesn't ship with a BLAS, so it tries to link to system BLAS by default (and that step is just in case a system BLAS isn't installed). You can build by linking to OpenBLAS, but I haven't tried linking the binary with |
|
Can you test if it works with openblas instead? Would rather not install things we don't need. And why do you need a login to download a binary, isn't arrayfire open source now? |
|
Yes it is, in that you can clone the library and build it from source. That's going to take time though. And the reason I don't automate building from source is that there are many ways you would do that depending on the hardware you have. |
|
For a minimum install, it turns out you don't need any of those libraries, so I'm removing ATLAS, FreeImage, etc. |
|
Fails because of this issue |
|
ArrayFire is really more than 650 MB? Why is it such a large download? |
|
They're bundling a number of libraries with it. Like CLBLAS, CLFFT, etc. |
|
We won't be testing any of those on PkgEval, will we? They don't have a smaller CPU-only version? |
|
No, they don't have anything lighter than this. |
|
I guess we can try this, but adding 650+ MB (that's just the download, then duplicated or more once installed?) to each worker VM might be a bit much. It's an open-source library, I think the best path forward is going to be just to build a CPU-only binary ourselves for testing purposes. |
|
Do you know if the shell script deletes itself after it's done? |
|
No it doesn't. Should I throw in a command to delete it after extraction? |
|
Yeah, I think that would be good. |
ArrayFire fails on PackageEvaluator. This should make it work.