Eric,
To recap the discussion, the lapack package is designed so that a user can
download the source, and build a locally-optimized atlas blas library from
source, then install it by copying the resulting dll's to /usr/local/bin. If
this optimization is not performed, a generic non-optimized blas
On Aug 9 06:04, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Any reason why lapack sticks .dlls in /usr/lib/lapack, then adds that
> directory to the path, rather than acting like all other packages and
> sticking .dlls directly in /usr/bin?
This has been discussed on
2 matches
Mail list logo
