Re: [Paraview] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7
Hello everyone, 4 Creating library E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.lib and object E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.exp 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_destroy referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlopenadvise referenced in function _dlopen_mpi_lib ... 4E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.dll : fatal error LNK1120: 8 unresolved externals Has anyone succeeded to recreate and solve above linking problems under Windows when using Python / OpenMPI with ParaView 3.8.1? Best regards, Nenad. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7
Hi Nenad, Turn OFF ENABLE_MPI4PY. Apparently there is a compatibility header in there that references symbols (_lt_dlopen...) that part of the gnu tool chain. I have to ask a higher power first, but most likely I will disable MPI4PY for Windows. Thank you for bringing this to our attention. On Thu, Jan 6, 2011 at 7:12 AM, Nenad Vujicic nena...@gmail.com wrote: Hello everyone, 4 Creating library E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.lib and object E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.exp 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_destroy referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlopenadvise referenced in function _dlopen_mpi_lib ... 4E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.dll : fatal error LNK1120: 8 unresolved externals Has anyone succeeded to recreate and solve above linking problems under Windows when using Python / OpenMPI with ParaView 3.8.1? Best regards, Nenad. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7
Hi Nenad, Sorry for not replying, Utkarsh just pointed your email out to me. Let me give this a try to see if I can recreate the problem. On Tue, Nov 23, 2010 at 6:00 PM, Nenad Vujicic nena...@gmail.com wrote: Hello everyone, I tried to compile ParaView 3.8.1 with BUILD_SHARED_LIBS, PARAVIEW_USE_MPI and PARAVIEW_ENABLE_PYTHON options turned on, but I get following linking errors: 4 Creating library E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.lib and object E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.exp 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_destroy referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlopenadvise referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_global referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_ext referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dladvise_init referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlinit referenced in function _dlopen_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlexit referenced in function _dlclose_mpi_lib 4MPI.obj : error LNK2019: unresolved external symbol __imp__lt_dlclose referenced in function _dlclose_mpi_lib 4E:\Projects\ParaView-3.8.1\build\bin\Release\MPIPython.dll : fatal error LNK1120: 8 unresolved externals I use Visual Studio 2008 SP1, CMake 2.8 and OpenMPI 1.4.3 (compiled with default options in Release mode). Same errors I get when trying to compile under CentOS 5.3 (with precompiled OpenMPI 1.4.3 sources) too. Other projects are compiled well in both cases. Does anyone knows how to solve this problem? I believe the solution is in setting appropriate building options for OpenMPI, but I'm not sure what to do. Thanks, Nenad. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Linking problems when compiling ParaView 3.8.1 with OpenMPI 1.4.3 and Python 2.7
Dear Dave, On Mon, Nov 29, 2010 at 4:45 PM, Dave Partyka dave.part...@kitware.com wrote: Hi Nenad, Sorry for not replying, Utkarsh just pointed your email out to me. Let me give this a try to see if I can recreate the problem. Thank You very much for Your help. It seems I made little mistake in previous message - everything builds fine under Linux, there is a problem only under Windows. I'm sorry for this mistake. Here is a list of steps I make under Windows: 1. Download OpenMPI 1.4.3. (from www.open-mpi.org) and ParaView 3.8.1 sources 2. I recompile OpenMPI with standard options in release mode: - mkdir build, cd build, cmake -DCMAKE_BUILD_TYPE:STRING=Release .., open .sln file and build solution in Release mode 3. I create OpenMPI NSIS package (cpack -G NSIS --config CPackConfig.cmake) and install it 4. I recompile ParaView sources with BUILD_SHARED_LIBS, PARAVIEW_USE_MPI and PARAVIEW_ENABLE_PYTHON options turned on: - mkdir build, cd build, cmake-gui .., open .sln file and build solution in Release mode - After the first configure, I set above 3 options, after the second I update following options: + MPI_EXTRA_LIBRARY ??libmpi.lib;??libmpi_cxx.lib;??libopen-pal.lib;??libopen-rte.lib * instead of ?? is full path to .lib file + MPI_INCLUDE_PATH C:/Program Files/OpenMPI_v1.4.3-win32/include + MPI_LIBRARY C:/Program Files/OpenMPI_v1.4.3-win32/lib/libmpi_cxx.lib I have Vista SP2, Visual Studio 2008 SP1 and Python 2.7 installed on problematic machine. Tell me if You need more informations. Best regards, Nenad. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
