patperry / lapack
- Source
- Commits
- Network (0)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Branch:
master
Patrick Perry (author)
Sat Jan 24 20:30:39 -0800 2009
lapack /
| name | age | message | |
|---|---|---|---|
 |
.gitignore | Loading commit data...  |
|
| |
COPYING | ||
| |
NEWS | Sat Jan 10 23:45:54 -0800 2009 | |
| |
README | Sat Jan 17 09:22:53 -0800 2009 | |
| |
Setup.lhs | Sat Jan 03 17:38:35 -0800 2009 | |
| |
TODO | Sat Jan 10 23:45:54 -0800 2009 | |
 |
cbits/ | ||
| |
configure.ac | Mon Jan 19 17:21:26 -0800 2009 | |
| |
lapack.buildinfo.in | ||
| |
lapack.cabal | Sat Jan 24 19:47:25 -0800 2009 | |
| |
lib/ | Sat Jan 24 20:30:39 -0800 2009 | |
| |
m4/ | Sat Jan 03 17:38:35 -0800 2009 | |
| |
tests/ | Sat Jan 24 20:30:39 -0800 2009 |
README
Building
========
To build the package, there is no need to run the configure script. Just
use the standard cabal commands:
runhaskell Setup.lhs configure
runhaskell Setup.lhs build
runhaskell Setup.lhs install
The package uses a script to find what BLAS and LAPACK libraries to link with.
To link with a custom BLAS, add the "--with-blas=<lib>" argument to --configure-option; to link with a custom LAPACK,
add the the
"--with-lapack=<lib>" argument. For example, do
runhaskell Setup.lhs configure --configure-option="--with-blas=<lib>"
To build this package from the repository, first run
aclocal -I m4
autoreconf
Thread-Safety
=============
The thread safety of the library depends on the thread-safety of the underlying
LAPACK implementation. You should note that the reference implementation of
LAPACK (which is what ATLAS uses) is *not* thread safe. Any routine which
modifies a read-only argument and then restores it is problematic. Potentially
dangerous functions which get used in the library include the following:
DORMQR, ZUNMQR.
