Thanks for your response. Now I get this error:
In file included from /home/miguel/petsc-3.4.4/include/petscsys.h:105:0,
from /home/miguel/petsc-3.4.4/include/petscbag.h:4,
from /home/miguel/petsc-3.4.4/include/petsc.h:5,
from ./include/libmesh/petsc_macro.h:93,
from src/base/libmesh.C:62:
/home/miguel/petsc-3.4.4/arch-linux2-c-debug/include/mpi.h:962:0: warning:
"MPI_REAL" redefined [enabled by default]
#define MPI_REAL OMPI_PREDEFINED_GLOBAL(MPI_Datatype, ompi_mpi_real)
^
In file included from ./include/libmesh/libmesh.h:25:0,
from src/base/libmesh.C:20:
./include/libmesh/libmesh_common.h:131:0: note: this is the location of the
previous definition
# define MPI_REAL MPI_DOUBLE
^
src/base/libmesh.C: In constructor 'libMesh::LibMeshInit::LibMeshInit(int,
const char* const*)':
src/base/libmesh.C:477:24: error: invalid conversion from 'int' to
'MPI_Comm {aka ompi_communicator_t*}' [-fpermissive]
PETSC_COMM_WORLD = libMesh::GLOBAL_COMM_WORLD;
^
In file included from /home/miguel/petsc-3.4.4/include/petscsys.h:1254:0,
from /home/miguel/petsc-3.4.4/include/petscbag.h:4,
from /home/miguel/petsc-3.4.4/include/petsc.h:5,
from ./include/libmesh/petsc_macro.h:93,
from src/base/libmesh.C:62:
/home/miguel/petsc-3.4.4/include/petscerror.h:249:175: error: invalid
conversion from 'int' to 'MPI_Comm {aka ompi_communicator_t*}'
[-fpermissive]
#define CHKERRABORT(comm,n) do {if (PetscUnlikely(n))
{PetscError(PETSC_COMM_SELF,__LINE__,PETSC_FUNCTION_NAME,__FILE__,__SDIR__,n,PETSC_ERROR_REPEAT,"
");MPI_Abort(comm,n);}} while (0)
^
src/base/libmesh.C:483:7: note: in expansion of macro 'CHKERRABORT'
CHKERRABORT(libMesh::GLOBAL_COMM_WORLD,ierr);
^
/home/miguel/petsc-3.4.4/include/petscerror.h:249:175: error: invalid
conversion from 'int' to 'MPI_Comm {aka ompi_communicator_t*}'
[-fpermissive]
#define CHKERRABORT(comm,n) do {if (PetscUnlikely(n))
{PetscError(PETSC_COMM_SELF,__LINE__,PETSC_FUNCTION_NAME,__FILE__,__SDIR__,n,PETSC_ERROR_REPEAT,"
");MPI_Abort(comm,n);}} while (0)
^
src/base/libmesh.C:505:11: note: in expansion of macro 'CHKERRABORT'
CHKERRABORT(libMesh::GLOBAL_COMM_WORLD,ierr);
^
make[1]: *** [src/base/libmesh_dbg_la-libmesh.lo] Error 1
make: *** [all-recursive] Error 1
MPI_REAL is redefined. I have another open mpi in /usr/local/ directory,
but I am linking with the one installed in the petsc directory:
--with-mpi=/home/miguel/petsc-3.4.4/externalpackages/openmpi-1.6.4
--with-cxx=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpicxx
--with-cc=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpicc
--with-fc=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpif90
Are they interfering with each other? Should I delete the one in
/usr/local/ ?
Thanks
Miguel
On Wed, May 14, 2014 at 12:32 PM, Kirk, Benjamin (JSC-EG311) <
[email protected]> wrote:
> If you don't need the exodus fortran wrappers (and if you're not sure, you
> likely don't), you can disable that feature easily enough:
>
> $ ./configure --help | grep exod
> --enable-exodus build with ExodusII API support
> --enable-exodus-fortran build with ExodusII Fortran API support
>
>
> so
>
> $ ./configure --disable-exodus-fortran
>
> should work.
>
>
> On May 14, 2014, at 12:22 PM, John Peterson <[email protected]> wrote:
>
> > On Wed, May 14, 2014 at 11:15 AM, Miguel Angel Salazar de Troya <
> > [email protected]> wrote:
> >
> >> I obtained the same error, then I also included mpif77
> >>
> >> --with-f77=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpif77
> >>
> >> and I obtained this
> >>
> >> make[2]: Entering directory
> >> `/home/miguel/libmesh/contrib/exodusii/5.22b/exodus'
> >> PPF77 forbind/src/libdbg_la-addrwrap.lo
> >>
> --------------------------------------------------------------------------
> >> Unfortunately, this installation of Open MPI was not compiled with
> >> Fortran 77 support. As such, the mpif77 compiler is non-functional.
> >>
> --------------------------------------------------------------------------
> >> make[2]: *** [forbind/src/libdbg_la-addrwrap.lo] Error 1
> >> make[2]: Leaving directory
> >> `/home/miguel/libmesh/contrib/exodusii/5.22b/exodus'
> >> make[1]: *** [all-recursive] Error 1
> >> make[1]: Leaving directory `/home/miguel/libmesh/contrib'
> >> make: *** [all-recursive] Error 1
> >>
> >> Before looking into how to fix this, I wanted to make sure that's going
> to
> >> be the problem. Am I in the right path?
> >>
> >
> > Apparently the Fortran bindings in Exodus require a F77 compiler... this
> is
> > unfortunate, but you might be able to do a quick "fix" by configuring
> with
> >
> > --with-f77=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpif90
> >
> > i.e. just using the "f90" compiler. On my system, all the mpifXX scripts
> > are gfortran with slightly different args anyway, so this has at least a
> > chance of working.
> >
> > --
> > John
> >
> ------------------------------------------------------------------------------
> > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> > Instantly run your Selenium tests across 300+ browser/OS combos.
> > Get unparalleled scalability from the best Selenium testing platform
> available
> > Simple to use. Nothing to install. Get started now for free."
> > http://p.sf.net/sfu/SauceLabs
> > _______________________________________________
> > Libmesh-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/libmesh-users
>
>
--
*Miguel Angel Salazar de Troya*
Graduate Research Assistant
Department of Mechanical Science and Engineering
University of Illinois at Urbana-Champaign
(217) 550-2360
[email protected]
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
