Missing Lapacke

[emengd]

Hi, trying to compile from source after pinning the repo with opam failed in a number of ways, and here is one simple problem I noticed (and another one in an issue to come): as in #104, I need to add --llapacke to src/owl/jbuild because my system's* binary openblas doesn't include lapacke. Is there any reason not to just add this permanently? If yes, anyone know if jbuilder can detect when it is needed?

* Linux Mint 18.2, based on Ubuntu 16.04

Edit: turns out my other issue is an opam bug. My version of opam puts C stubs in a directory named "stubslibs" but looks from them in "stublibs". -_- (cf #144)

[jnavila]

FWIW, I tried on my debian testing, but the openblas provided by the packages is truncated and missing some functions (I don't understand why) such as _clagge. I ended up using the provided docker for testing.

[igarnier]

It's not an easy problem: I compiled openblas from sources and they include lapacke; I then had to perform the opposite (remove -llapacke from some build config file) for owl to compile. I also previously encountered the same problem as @jnavila when using the version of openblas bundled with my OS. A "solution" would be to have a script that checks which symbols are exported by the currently installed openblas.

[pveber]

FWIW, I tried on my debian testing, but the openblas provided by the packages is truncated and missing some functions (I don't understand why) such as _clagge.

I just observed the same thing for ubuntu bionic (18.04). I ended up installing openblas by hand (with gfortran installed, so that lapacke is included) and it worked easily.

[ryanrhymes]

-llapacke is a bit hacking, because the binary installation of openblas on some platforms don't include lapack. Installing from openblas source is the best option. I have removed -llapacke from configure.ml, see #344