I solved the problem and the quote 'we have met the enemy and he is
us' fits prefectly.
The reason was I had a stale object file laying around from when i
used a different compiler. Removing mpif.h as they are listed in the
PARPACK ARmake.inc and recompiling worked.
Sorry for the red her
Yes, the software came with its own. And i removed it, mpif77 takes
care of not having mpif.h in the directory just as it should.
I should mention (sorry) that the single, complex and double complex
examples work. only the double (real) examples fail.
Brock Palen
Center for Advanced Comp
This *usually* happens when you include the mpif.h from a different
MPI implementation. Can you check that?
On Dec 12, 2007, at 5:15 PM, Brock Palen wrote:
Has anyone ever built parpack (http://www.caam.rice.edu/software/
ARPACK/) with openmpi? It compiles but some of the examples give:
[
Has anyone ever built parpack (http://www.caam.rice.edu/software/
ARPACK/) with openmpi? It compiles but some of the examples give:
[nyx-login1.engin.umich.edu:12173] *** on communicator MPI_COMM_WORLD
[nyx-login1.engin.umich.edu:12173] *** MPI_ERR_TYPE: invalid datatype
[nyx-login1.engin.umic
