"Bryan O'Sullivan" <[EMAIL PROTECTED]> writes:
> Judah Jacobson wrote:
>
>> My preference is to use an autoconf script to solve that problem.
>> ("build-type: Configure" in the cabal file.)
>
> That approach would not work well for BLAS. The various BLAS libraries
> have profoundly different performance characteristics, and you wouldn't
> want to get the wrong one for your system, if you had both installed.
Is the blas library linked statically? It looks to me that
the binary is dynamically linked.
linux-vdso.so.1 => (0x00007fff003fe000)
libgsl.so.0 => /usr/lib/libgsl.so.0 (0x00002af4aa8cc000)
libblas.so.0 => /usr/lib/libblas.so.0 (0x00002af4aac91000)
liblapack.so.0 => /usr/lib/liblapack.so.0 (0x00002af4aaeb0000)
libutil.so.1 => /lib/libutil.so.1 (0x00002af4ab612000)
libdl.so.2 => /lib/libdl.so.2 (0x00002af4ab815000)
libm.so.6 => /lib/libm.so.6 (0x00002af4aba19000)
libgmp.so.3 => /usr/lib/libgmp.so.3 (0x00002af4abc9b000)
librt.so.1 => /lib/librt.so.1 (0x00002af4abedb000)
libc.so.6 => /lib/libc.so.6 (0x00002af4ac0e4000)
libgslcblas.so.0 => /usr/lib/libgslcblas.so.0 (0x00002af4ac424000)
libgfortran.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/libgfortran.so.1 (0x00002af4ac654000)
libatlas.so.0 => /usr/lib/libatlas.so.0 (0x00002af4ac8eb000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00002af4ad123000)
libcblas.so.0 => /usr/lib/libcblas.so.0 (0x00002af4ad33e000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002af4ad55d000)
/lib64/ld-linux-x86-64.so.2 (0x00002af4aa6b0000)
And presumably the various BLAS implementations share
identical interface. You can still change the library at
run-time with LD_LIBRARY_PATH. Or am I missing something?
Xiao-Yong
--
c/* __o/*
<\ * (__
*/\ <
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
