[Paraview-developers] ParaView Build problem

[Utkarsh Ayachit]

Paul,

I've been helping Hanumantha off the list. The MPI issue stems from
the fact that he was using old MPI_* variables for CMake e.g.
MPI_LIBRARY, MPI_EXTRA_LIBRARY. When specified, CMake can end up in
weird cases. The recommended way is to use the newer variables, viz.

#   MPI_<lang>_COMPILER        MPI Compiler wrapper for <lang>
#   MPI_<lang>_COMPILE_FLAGS   Compilation flags for MPI programs
#   MPI_<lang>_INCLUDE_PATH    Include path(s) for MPI header
#   MPI_<lang>_LINK_FLAGS      Linking flags for MPI programs
#   MPI_<lang>_LIBRARIES       All libraries to link MPI programs against

Where <lang> is C,CXX or Fortran. Typically, just specifying the
MPI_C_COMPILER and MPI_CXX_COMPILER correctly will do the trick (as
was the case with this particular issue).

Utkarsh


On Tue, Jul 2, 2013 at 5:28 PM, Paul Edwards <paul.m.edwards at gmail.com> wrote:
> Hi Hanumantha,
>
> Did you fix this?  You could try adding /usr/lib64/libdl.so to your
> MPI_EXTRA_LIBRARY (separated with a semicolon).
>
> Regards,
> Paul
>
> On 1 July 2013 14:31, Pandu tech <pandu4tech at gmail.com> wrote:
>> Hi,
>>
>> I tried to build the latest paraview, but it gave me the following errors.
>>
>> I work on SuSe 12.1 and some of the details are given below:
>>
>> which mpicc gives /usr/lib64/mpi/gcc/openmpi/bin/mpicc
>>
>> MPI_DIR is /usr/lib64/mpi/gcc/openmpi/
>>
>> MY cmake variables set like this:
>>
>> -DMPI_LIBRARY=${MPI_DIR}/lib/libmpi.so \
>> -DMPI_COMPILER=${MPI_DIR}/bin/mpicc \
>> -DMPI_EXTRA_LIBRARY=${MPI_DIR}/lib/libmpi_cxx.so \
>> -DMPI_INCLUDE_PATH=${MPI_DIR}/include \
>>
>> =======================ERROR
>> MESSGAE=================================================================
>> mpi.so /usr/lib64/mpi/gcc/openmpi/lib/libmpi_cxx.so
>> -Wl,-rpath,/home/rruser/ss02/install/bin/ss02/lib:/usr/lib64/mpi/gcc/openmpi/lib
>> CMakeFiles/mpi4py.MPI.dir/src/MPI.c.o: In function `OPENMPI_dlopen_libmpi':
>> /home/rruser/ss02/source/src/RollsRoyceParaView/ThirdParty/mpi4py/vtkmpi4py/src/compat/openmpi.h:71:
>> undefined reference to `dlopen'
>> /home/rruser/ss02/source/src/RollsRoyceParaView/ThirdParty/mpi4py/vtkmpi4py/src/compat/openmpi.h:72:
>> undefined reference to `dlopen'
>> /home/rruser/ss02/source/src/RollsRoyceParaView/ThirdParty/mpi4py/vtkmpi4py/src/compat/openmpi.h:73:
>> undefined reference to `dlopen'
>> /home/rruser/ss02/source/src/RollsRoyceParaView/ThirdParty/mpi4py/vtkmpi4py/src/compat/openmpi.h:74:
>> undefined reference to `dlopen'
>> /home/rruser/ss02/source/src/RollsRoyceParaView/ThirdParty/mpi4py/vtkmpi4py/src/compat/openmpi.h:75:
>> undefined reference to `dlopen'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lib/site-packages/mpi4py/MPI.so] Error 1
>> make[2]: Leaving directory `/home/rruser/ss02/build/paraview-build'
>> make[1]: *** [ThirdParty/mpi4py/vtkmpi4py/CMakeFiles/mpi4py.MPI.dir/all]
>> Error 2
>> make[1]: Leaving directory `/home/rruser/ss02/build/paraview-build'
>> make: *** [all] Error 2
>>
>>
>>
>> Please share your suggestions regarding this.
>>
>> Thanks,
>> Pandu.
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers