I just started using lapack with Visual Studio and Borland compilers, and have some problems. (I leave out the Borland ones for now)
a) compiling clapack 3.2.1using CMake -> seem to only give me a static lib (is that right?) And the "install" target don't work.
b) downloaded the 32bits dll's from http://icl.cs.utk.edu/lapack-for-window ... index.html
(in the docs it says you need libgfortran-3.dll
. But that file don't exists in a cygwin installation. On my system it is called cyggfortran-3.dll
. I just copied this and named it libgfortran-3.dll and that seemed to work?
Now, my application, that only uses two functions dgeqp3_
give different result, depending on if I link with the static libe (3.2.1) or using the DLL.
With the static lib, my app runs fine, but the result is different from when linking with the DLL. (I'll try to post output later on here, unfortunately the application is a little convoluted at the moment)
When linking with the DLL, everything works fine, except when the application exits. When it exits, the app has to be manually killed, and a core dump is emitted. I'm using Visual Studio 2010.
Any feedback on this is welcomed. Have anyone else observed the core dump problem with the prebuilt dll's?
Also, why are not the corresponding header files not published together with the lib and the dll on the lapack-for_windows page?. Its crucial that they are matching, I would think.