Re: [Libmesh-users] Libmesh and MPICH2

[Cody P. <cod...@gm...>]

Please send details on your system, OS and your configure options and we may
be able to see where the problem lies.

Cody

On Sat, Jul 10, 2010 at 11:39 AM, Derek Gaston <fri...@gm...> wrote:

> I don't know exactly what the problem is here.... But I thought I
> would let you know that we use MPICH2 with Petsc and libmesh
> everyday... On both 64bit macs and Linux... And everything works fine.
>
> So it is possible.  Sorry I've never seen this error before... Maybe
> Cody can help....
>
> Derek
>
> Sent from my iPad
>
> On Jul 10, 2010, at 7:10 AM, John Peterson
> <pet...@cf...> wrote:
>
> > On Fri, Jul 9, 2010 at 9:47 PM, Yujie <rec...@gm...> wrote:
> >> Dear Libmesh Developers
> >>
> >> I am updating MPICH from MPICH1 to MPICH2. I can compile PETSc and
> >> Libmesh successfully. I also use "make test" to successfully test
> >> PETSc. However, when I run my codes with mpiexec. I got the following
> >> errors
> >> "
> >> 0 - <NO ERROR MESSAGE> : Could not convert index 1140850688 into a
> pointer
> >> The index may be an incorrect argument.
> >> Possible sources of this problem are a missing "include 'mpif.h'",
> >> a misspelled MPI object (e.g., MPI_COM_WORLD instead of MPI_COMM_WORLD)
> >> or a misspelled user variable for an MPI object (e.g.,
> >> com instead of comm).
> >> [0]  Aborting program !
> >> [0] Aborting program!
> >> p0_17843:  p4_error: : 9039
> >> p0_17842:  p4_error: : 9039
> >> 0 - <NO ERROR MESSAGE> : Could not convert index 1140850688 into a
> pointer
> >> The index may be an incorrect argument.
> >> Possible sources of this problem are a missing "include 'mpif.h'",
> >> a misspelled MPI object (e.g., MPI_COM_WORLD instead of MPI_COMM_WORLD)
> >> or a misspelled user variable for an MPI object (e.g.,
> >> com instead of comm).
> >> [0]  Aborting program !
> >> [0] Aborting program!
> >> p0_23019:  p4_error: : 9039"
> >>
> >> Could you give me some comments? thanks a lot.
> >
> > Hi,
> >
> > If I recall correctly, this is a problem with the Fortran side of the
> > mpich1 implementation storing the address of a pointer as a 4 byte
> > integer.  This does not work on 64-bit systems where pointers are 8
> > bytes...if you google the error message you'll get more information.
> >
> > You say you are switching to mpich2 though... so I'm not even sure why
> > you would be seeing this error.  My advice is to let petsc download
> > MPI for you during it's installation.  That has worked for me in the
> > past.
> >
> > --
> > John
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Libmesh-users mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libmesh-users
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Libmesh-users mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-users
>