[Paraview] Lam mpi + paraview

Fri Jun 22 12:55:56 EDT 2007

I'm using Paraview 2.6, and here are the configuration options for 
compilers and mpi.  If you want to see more of my configuration, let me 
know.  I spent quite awhile messing around with these, especially to get 
distcc workking (our cluster contains lots of 7 year old nodes... only 
together do they actually have notable computing power, and compiling on 
one node would've taken forever). One important thing was that this did 
NOT compile correctly with the new gcc that we have (gcc-4.2 I believe) so 
we used the older one.

//C compiler.
CMAKE_C_COMPILER:FILEPATH=/usr/lib/distcc/bin/gcc-3.4
[ which is linked to the normal distcc, with the "gcc-3.4" binary in our 
PATH ]

//CXX compiler.
CMAKE_CXX_COMPILER:FILEPATH=/usr/lib/distcc/bin/g++-3.4
[ which is linked to the normal distcc, with the "g++-3.4" binary in our 
PATH ]

//If a second mpi library is necessary, specify it here.
MPI_EXTRA_LIBRARY:FILEPATH=/usr/lib/libmpi++.so
//Path to a file.
MPI_INCLUDE_PATH:PATH=/usr/local/mpich/1.2.5.2/gnu/include
//Path to a library.
MPI_LIBRARY:FILEPATH=/usr/lib/libmpi.so
[ CMake figured these out on its own. We compiled and installed our own 
mpich, not (mpich-)mpd. ]

Hope this helps,
~Kyle

> Message: 3
> Date: Fri, 22 Jun 2007 12:31:01 -0400
> From: "Robert Maynard" <thorin.hax at gmail.com>
> Subject: Re: [Paraview] Lam mpi + paraview
> To: paraview at paraview.org
> Message-ID:
>    <b45d6a1e0706220931n2ab240cdh1ccfa63a92ecb5e9 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> My first attempt at getting MPI working with paraview was by using the
> default compiler and setting the MPI_INCLUDE_PATH and MPI_LIBRARY paths. 
The
> problem I was running into was that I was getting underfined references 
when
> linking the mpi libraries. The solution that Lam recommended was to use
> their compiler to solve the library problems. If somebody could send me
> their MPI_INCLUDE_PATH and MPI_LIBRARY configurations it would help me 
out
> alot.
> 
> On 6/22/07, David E DeMarle <dave.demarle at kitware.com> wrote:
> >
> > That is odd.
> >
> > I have a feeling that lam's mpicc brings in or leaves out something
> > important in the compilation and linking, especially when it compiles 
the
> > non parallel paraview app. When compiling against MPICH for example we 
don't
> > use MPICH's mpicc. But instead use normal cc and link in the extra
> > libraries. Instead of setting the compiler directly, have you tried 
just
> > turning on PARAVIEW_USE_MPI and then setting the MPI_INCLUDE_PATH and
> > MPI_LIBRARY instead?
> >
> > cheers
> > Dave
> >
> >
> >
> > On 6/22/07, Robert Maynard <thorin.hax at gmail.com> wrote:
> > >
> > > the backtrace seems really short to me, I did compile paraview with 
the
> > > Debug flag.
> > >
> > > Program received signal SIGFPE, Arithmetic exception.
> > > 0x03d79ac6 in ?? ()
> > > (gdb) backtrace
> > > #0  0x03d79ac6 in ?? ()
> > > #1  0x00000000 in ?? ()
> > > (gdb)
> > >
> > > On 6/22/07, David E DeMarle < dave.demarle at kitware.com> wrote:
> > > >
> > > > I was thinking of a stack dump not a system call trace. In gdb 
after
> > > > the crash type backtrace and send that output to the list.
> > > >
> > > > Thanks Robert.
> > > > Dave
> > > >
> > > > On 6/22/07, Robert Maynard <thorin.hax at gmail.com> wrote:
> > > > >
> > > > > Sure I have attached the strace output
> > > > >
> > > > >
> > > > > On 6/22/07, David E DeMarle < dave.demarle at kitware.com> wrote:
> > > > > >
> > > > > > Can you send a stack trace for the floating point exception?
> > > > > >
> > > > > >
> > > > > > On 6/22/07, Robert Maynard <thorin.hax at gmail.com > wrote:
> > > > > > >
> > > > > > > Yes i understand I have to link to the server in MPI now, 
but as
> > > > > > > my first email stated, by I trying running the client 
> now that I compiled
> > > > > > > mpi support in, I get a runtime floating point exception
> before paraview
> > > > > > > launches.
> > > > > > >
> > > > > > > On 6/22/07, David E DeMarle <dave.demarle at kitware.com > 
wrote:
> > > > > > > >
> > > > > > > > In 3.0 the paraview executable is not MPI parallel, only 
the
> > > > > > > > server executables are.
> > > > > > > > That is, you can no longer run "mpirun -np N paraview" but
> > > > > > > > instead have to do something like "mpirun -np N 
> pvserver&; paraview" and
> > > > > > > > then use File->Choose Server to connect to the parallel 
server.
> > > > > > > >
> > > > > > > > cheers
> > > > > > > > Dave DeMarle
> > > > > > > >
> > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > ParaView mailing list
> > > > > > > ParaView at paraview.org
> > > > > > > http://www.paraview.org/mailman/listinfo/paraview
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > ParaView mailing list
> > > > > ParaView at paraview.org
> > > > > http://www.paraview.org/mailman/listinfo/paraview
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > > _______________________________________________
> > > ParaView mailing list
> > > ParaView at paraview.org
> > > http://www.paraview.org/mailman/listinfo/paraview
> > >
> > >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://public.kitware.
> com/pipermail/paraview/attachments/20070622/4eed4dc3/attachment.html
> 
> ------------------------------
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
> 
> 
> End of ParaView Digest, Vol 38, Issue 52
> ****************************************

The server made the following annotations 
---------------------------------------------------------------------------------
This message contains information that may be privileged or confidential and is the property of Beckman Coulter, Inc. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

---------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20070622/59b1b3e1/attachment.htm