Hmm... https://netlib.org/lapack/index.html points me at https://icl.utk.edu/lapack-for-windows/lapack/ which leads me to https://icl.utk.edu/lapack-for-windows/lapack/index.html#libraries
Specifically, for 64 bit, the links https://icl.utk.edu/lapack-for-windows/libraries/VisualStudio/3.7.0/Dynamic-MINGW/Win64/liblapack.dll and https://icl.utk.edu/lapack-for-windows/libraries/VisualStudio/3.7.0/Dynamic-MINGW/Win64/libblas.dll And, after downloading liblapack.dll, I see: $ strings liblapack.dll | grep ilaver ilaver_ ilaver.f ilaver_ So I'm not quite sure what's gone wrong here, with the prebuilt lapack. Where did J's liblapack3.dll come from? Thanks, -- Raul On Sat, Apr 8, 2023 at 9:29 AM bill lam <[email protected]> wrote: > > Use the official lapack 3.x from netlib.org, all others are dead ends. > > Please also build an optimized blas if possible. > > On Sat, Apr 8, 2023 at 9:22 PM Raul Miller <[email protected]> wrote: > > > Huh... looking at https://netlib.org/liblist.html I see: > > > > *) lapack > > > > *) lapack++ from https://math.nist.gov/lapack++/ superseded by > > https://math.nist.gov/tnt/ > > > > *) lapack3e upgraded to support features of fortran77 and fortran90 > > > > *) lapack90 (404) > > > > *) clapack (lapack after being preprocessed by f2c -- probably better > > to use lapack) > > > > *) scalapack recently maintained, windows dlls available from > > https://icl.utk.edu/lapack-for-windows/scalapack/ > > > > I guess before I dive into this, I should understand the changes from > > J's original lapack distribution and lapack2 distribution. Which of > > these repositories have we been using? > > > > Thanks, > > > > -- > > Raul > > > > > > > > On Sat, Apr 8, 2023 at 9:12 AM Raul Miller <[email protected]> wrote: > > > > > > Hmm.... > > > > > > https://www.fi.muni.cz/~xsvobod2/misc/lapack/ says that no native open > > > source fortran compiler is available for windows. > > > > > > But that's an old page, which might be why it ignores > > > https://gcc.gnu.org/wiki/GFortranBinariesWindows > > > > > > I'll see if I can get that to work. > > > > > > Thanks, > > > > > > -- > > > Raul > > > > > > On Sat, Apr 8, 2023 at 5:28 AM bill lam <[email protected]> wrote: > > > > > > > > Unfortunately the pre-built windows lapack binaries over the net are > > > > outdated. > > > > It is easier to modify the jwiki documentation than to find an updated > > > > binary. > > > > > > > > On Fri, Apr 7, 2023 at 8:30 AM Igor Zhuravlov <[email protected]> > > wrote: > > > > > > > > > On Thu, Apr 6, 2023 at 02:30 PM Ric Sherlock <[email protected]> > > wrote: > > > > > > However the new section about how to identify a LAPACK version > > doesn't > > > > > work > > > > > > on Windows: > > > > > > > > > > > > ilaver_jlapack2_ (,0);(,0);(,0) > > > > > > > > > > > > |domain error in cd, executing dyad 15!:0 > > > > > > | > > > > > > | ilaver_jlapack2_(,0);(,0);(,0) > > > > > > > > > > It turned out that liblapack.dll (file size: 5181440 bytes) > > downloaded > > > > > from > > > > > jsoftware.com doesn't contain ilaenv_ subroutine. > > > > > > > > > > This library should be rebuilt. > > > > > > > > > > -- > > > > > Regards, > > > > > Igor > > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > For information about J forums see > > http://www.jsoftware.com/forums.htm > > > > > > > > > ---------------------------------------------------------------------- > > > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
