[Paraview] Lam mpi + paraview

Berk Geveci berk.geveci at kitware.com
Fri Jun 22 12:48:47 EDT 2007


Do not use mpicc and mpic++ to compile paraview. Instead, configure
the build such that the necessary mpi libraries are used and the
appropriate include paths are set. mpicc and mpic++ are light wrappers
around the actual compilers that do "extra stuff". If you use them to
compile paraview, they do that "extra stuff" to every single object
file they compile. Since there is a good chunk of code that do not use
MPI, it is best to avoid doing that.

On 6/22/07, Robert Maynard <thorin.hax at gmail.com> wrote:
> I have compiled paraview with mpi support using lam. I changed the standard
> c and c++ compilers for paraview too mpicc and mpic++ so that all the
> mpi references where aviable. The build was correctly compiled, the problem
> comes when trying to launch the standalone version of paraview.
>
> When launching /bin/paraview the error i get is "Floating point exception",
> using gdb to trace the error I get
>   New process 16350]
>
>  Program received signal SIGFPE, Arithmetic exception.
>  0x05761ac6 in ?? ()
>
> Now if I try to run /bin/paraview with mpirun -np 1, it tells me that
> paraview  did not invoke MPI_INIT before quitting. The problem seems to only
> happen with standalone version, as /bin/pvserver runs perfectly fine with
> mpirun
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
>


-- 
 Berk Geveci
 Kitware Inc.
 28 Corporate Drive
 Clifton Park, NY, 12065


More information about the ParaView mailing list