Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- From: Merlin.Piedragon@xxxxxxxxx
- Date: Fri, 18 Jan 2008 15:26:30 -0800 (PST)
On Jan 17, 4:52 pm, "FX" <coud...@xxxxxxxxxxxxx> wrote:
What problem? With no glass orb, it's a bit difficult...
eh? LAPACK make failure, as stated.
What is the error message? It should work straight out-of-the-box. You
have to understand: I'm ready to spend yet some more of my sleep time to
investigate it, download LAPACK, compile it and see what the error
message is, but that seems pointless as you could just copy-paste it
here.
The make problem might be unique to Windows?
Possibly. Anything case-sensitive (.f vs .F) in the LAPACK files?
--
FX
"Should" work? heh. So, what you're saying is: none of you folks
actually use Windows? LOL.
C:\Programs\lapack-3.1.1>make
( cd INSTALL; make; ./testlsame; ./testslamch; \
./testdlamch; ./testsecond; ./testdsecnd; ./testversion )
process_begin: CreateProcess((null), ( cd INSTALL; make; ./
testlsame; ./testslam
ch; ./testdlamch; ./testsecond; ./testdsecnd; ./testversion ), ...)
failed.
make (e=2): The system cannot find the file specified.
make: *** [lapack_install] Error 2
Don't trouble yourself FX, I know what the problem is and it isn't
your fault. You provide a nice gfortran distro for Windows which
includes make.exe, which I am delighted to be using. As jaw-dropping
as it may seem, the reality is that the windows port of gnu make.exe
apparently has a a few quirks, it works pretty well, but not
perfectly, so that the LAPACK makefiles fail, and potentially others
makefiles may also fail.
As I mentioned earlier, the instruction ( cd INSTALL;
instruction1; .... ) does not properly execute in the Windows port of
gnu make. This can be confirmed by downloading official ports (eg
mingw) and trying them. It should work, the make documentation says it
should work, but on windows it doesn't. This instruction is used in
LAPACK makefiles, and as a result these fail under the windows port of
gnu make. [Whether Cygwin works or not, I know not.] Now, we can tell
the gnu make team, ask then to hurry up and fix it, but in the
meantime, since we have no fountain pen, perhaps we can use the pencil
(workaround)?
What I've discovered does work is an alternate form (cd INSTALL &&
instruction1 ). To make LAPACK requires modification of the make.inc,
per usual, and modification of two makefiles. It also requires,
relevant to a gfortran issue (to be mentioned later) minor
modification of two of the test routines. Some instructions also need
to be provided plus Copyright Notice. Seven text files.
This is a specialized, but very annoying problem for windows users of
gfortran. As the distributer of gfortran binaries for Windows which
includes a make.exe for which this problem applies, and as a member of
gcc.org, you have some interesting alternatives which include: You can
elect to do nothing while someone else documents a problem in your
distro (:^@), you can consider including an advisory or patch files in
your distro or on your site, which I am prepared to help do if you
wish, or you can use your contacts in gcc.org to encourage a fix in
make.
-Pi
.
- Follow-Ups:
- References:
- Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- From: Merlin . Piedragon
- Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- From: FX
- Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- From: Merlin . Piedragon
- Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- From: FX
- Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- Prev by Date: Re: Several questions about character C binding
- Next by Date: Re: Several questions about character C binding
- Previous by thread: Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- Next by thread: Re: Building BLAS/LAPACK libraries with gfortran (mingw) on Windows
- Index(es):
Relevant Pages
|
