I am not sure if this is possible. If you are working with Fortran, then
why don't you want to use MUMPS?
What a compiler do you use on XP?
Recently on the MUMPS list there was a discussion on how to use WinMUMPS
to compile MUMPS with these compilers. Alternatively you can use my text
http://matrixprogramming.com/MUMPS/
on how to compile MUMPS with GNUMake.
This should be much easier that to try to call TAUCS from Fortran.
The formats for GNUmake and NMake are different. It is impossible to use
makefiles directly without editing.
> ':' or '=' separator Stop. I couldn't use Cygwin because of the error:
> ifort:command not found
You have to setup VS for Cygwin. Please look at
http://matrixprogramming.com/Tools/UseVisualStudio.html
Well, you have to extend the variable to work with Intel Fortran.
Have you changed Makefile in examples?
http://matrixprogramming.com/MUMPS/examples/Makefile
It seems that you use the old one. And without changes it does now work
with MS VS.
Alternatively you can use *.lib and compile the example directly with GUI.
Note that you will need METIS lib and BLAS to link MUMPS.
The warning can be ignored. But why you have --o, hard to say. Please
have a look at the command. It should actually correspond to this line
$(FL) -o $@ $(OPTL) $@.o $(LIBDMUMPS) $(LIBM) $(LIBBLAS) $(LIBOTHERS)
$(LORDERINGS)
The simplest to find the command, to copy it and then to edit manually.
If you write me the command that you receive, than I can tell you more
exactly what happened.
This is a conflict between -MD and -MT
> It seems that I didn't use the right libmetis.lib. Can you send me a copy
> which can be used in Windows.
> The libmetis.lib I used were MS windows binaries downloaded from METIS's
> homepage.
It is quite simple to compile METIS with MS VS - see
http://matrixprogramming.com/METIS/
-MD is already in the makefile, so it should work.
There are three different run-time libraries by MS VS. Well, I think
that now there are only two: it seems that -ML is not supported anymore.
There are problems when one compiles different pieces with different
run-times. Then there is a conflict.
It has nothing to do with the speed but rather with the way how system
libraries are called from the application. You can find more info at
Microsoft Technet.