nilsbecker

ok, cleared up: the issue was that the ventura upgrade did not also upgrade the commandline tools. after installing these again as described above, pkg-config points to a libffi path...

I would very much welcome such a PR. I am used to setting linking and C flag variables for installing lacaml and gsl, and it works well there to use...

i just tied https://github.com/owlbarn/owl/issues/625#issuecomment-1312197649 and that worked for me -- i guess it's using your updated arm64 branch yes?

On another M1 mac I tried the same but keep getting a linker error that says `ld: library 'lapacke' not found`. any hints? `brew install lapack` did not help so...

> OWL_DISABLE_LAPACKE_LINKING_FLAG=1 indeed that did allow it to install! the working command line was: `PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig" OWL_DISABLE_LAPACKE_LINKING_FLAG=1 opam install owl.1.1.0` i.e. without adding a path to the separately installed lapack library....

ok, while disabling the lapacke linking did allow owl to get installed, it then does not work properly in an application. i get loads of linking errors saying that some...

no that should not be the problem. i did a rebuild of the homebrew installation from an exported package list. i just noticed that i have an env variable set:...

i think the manual linking flags were from a previous workaround for installing owl. i just retried with `LDFLAGS=$OWL_MANUAL_LDFLAGS opam install owl.1.1.0` but that did not remove the lapacke linking...

Ok, I've got it now. Mea culpa. For a reason I cannot fathom, my full opam switch was an x86_64 binary without me knowing it. It silently ran under Rosetta2...

yes, sorry i meant `Accu`. disclaimer: i have not actually used it, just browsed the interface. i agree that the auto-binning is very useful, and any more general histogram should...