Re: [Paraview] static linking with python
On 03/05/2011 02:25 PM, burlen wrote: OK but why would LINK_SEARCH_END_STATIC result in -Wl,-Bstatic -Wl,-Bdynamic being used ? Shouldn't it be just -Bstatic ? You can read the logic in cmComputeLinkInformation.cxx to figure this out. Why is CMake's default to make a substitution like -lfoo with -Bdynamic -lfoo? The default assumption is dynamic linking but if one specifies a full path to a static library like /usr/lib/libm.a then it switches to -Bstatic to pick that up with -lm and then back to -Bdynamic. Static linking was not a goal at the time that stuff was written. Thank you Brad! I tried the new feature and I still have a -Bdynamic appearing in the middle of the link line I think the only way that can happen now is if you actually pass a .so file to target_link_libraries (assuming LINK_SEARCH_START_STATIC is on) that is in /usr/lib or another system directory. Check your CMakeCache for such entries. Really want to control things then bring all external libraries in as IMPORTED targets and set the IMPORTED_LOCATION property to point at the full path to the exact file you want. -Brad ___ 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] static linking with python
On 03/08/2011 05:08 AM, Brad King wrote: I think the only way that can happen now is if you actually pass a .so file to target_link_libraries (assuming LINK_SEARCH_START_STATIC is on) that is in /usr/lib or another system directory. Check your CMakeCache for such entries. I do have LINK_SEARCH_START_STATIC TRUE. I do see a ton of .so all are related to x11, but I have VTK_USE_X=OFF. No libm.so in the Cache though. I guess this might be some unexpected interaction between PV's cmake scripts and cmake's linking logic. It only happens when python support is enabled. I'm using PV 3.8.1. Dave DeMarle said he didn't have this problem with a recent version of PV, and also that he's working on officially supporting static link with python for release 3.10.1. The Cray's do support dynamic linking , although it looks like there is a performance penalty at least during startup, I'm going to take that route since it works, and won't be too long until static linking + python is officially supported. Thanks for the help Burlen ___ 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] static linking with python
On 03/04/2011 05:53 AM, Brad King wrote: On 03/03/2011 04:08 PM, Burlen Loring wrote: On 03/03/2011 05:39 AM, Brad King wrote: On 03/02/2011 06:31 PM, Burlen Loring wrote: Can anyone help figure out where these comes from and how to turn them off? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LINK_SEARCH_END_STATIC Thanks for the reply, I have been playing with this unsuccessfully. It doesn't have the desired effect so I think I'm doing something wrong. Make uses these options to set the link type for libraries whose full paths are not known or (in some cases) are in implicit link directories for the platform. By default the linker search type is left at -Bdynamic by the end of the library list. IOW any library of the form -lfoo is assumed to be -Bdynamic. Libraries in implicit link directories like /usr/lib/libbar.a will get turned into -Bstatic -lbar but then a later -lfoo will become -Bdynamic -lfoo since -lfoo is assumed to be dynamic. This is all because CMake assumes dynamic linking is preferred. OK but why would LINK_SEARCH_END_STATIC result in -Wl,-Bstatic -Wl,-Bdynamic being used ? Shouldn't it be just -Bstatic ? Why is CMake's default to make a substitution like -lfoo with -Bdynamic -lfoo ? It seems like this choice is unnecessarily complicating things. It's also often redundant (as long as you don't want to mix static and dynamic linking) because without this ld defaults to using shared libraries. These substitutions override what's set in CMAKE_EXE_LINKER_FLAGS making that pretty much useless. It would be useful to be able to turn off these substitutions, then the -static in CMAKE_EXE_LINKER_FLAGS would work. I wondering if the LINK_SEARCH_*_STATIC issues are sidetracking us, because there's one instance of -Bdynamic appearing in the middle of the link line (below), and it's not affected by LINK_SEARCH_*_STATIC. I have no idea where it's coming from but it's presence is related to enabling python support because otherwise pv links statically fine. By the way this is a statically linked build of python. Now you can set a LINK_SEARCH_START_STATIC property to switch the dynamic linking assumption to static linking. In combination with -static that should produce a link line with no -Bdynamic options that links statically. This new feature should be available in the nightly builds by tomorrow: Thank you Brad! I tried the new feature and I still have a -Bdynamic appearing in the middle of the link line at ../../bin/libhdf5.a -Wl,-Bdynamic -lm ../../bin/libvtkPVCommandOptions.a, full link line from the LINK_SEARCH_START_STATIC build follows. cat ./Servers/Executables/CMakeFiles/pvserver.dir/link.txt /opt/cray/xt-asyncpe/4.0/bin/CC-Wno-deprecated -fPIC -Bstatic -static -O3 -DNDEBUG -fPIC -Bstatic -static CMakeFiles/pvserver.dir/pvserver.cxx.o -o ../../bin/pvserver -rdynamic -L/opt/fftw/3.2.2.1/lib -L/opt/cray/pmi/1.0-1..8256.50.1.ss/lib64 -L/opt/cray/mpt/5.0.0/xt/seastar/mpich2-gnu/lib -L/opt/cray/mpt/5.0.0/xt/seastar/sma/lib64 -L/opt/xt-libsci/10.4.5/gnu/lib/44 -L/opt/xt-libsci/10.4.5/gnu/lib -L/opt/xt-pe/2.2.48B/lib -L/opt/xt-pe/default/lib -L/opt/xt-pe/2.2.48B/lib/snos64 -L/opt/xt-pe/default/lib/snos64 -L/opt/gcc/4.4.4/snos/lib/gcc/x86_64-suse-linux/4.4.4 -L/opt/gcc/4.4.4/snos/lib64 -L/lib64 -L/opt/gcc/4.4.4/snos/lib ../../bin/libvtkPVServerCommon.a ../../bin/libvtkPVFilters.a ../../bin/libvtkPVServerManager.a ../../bin/libvtkPVPythonInterpretor.a ../../bin/libvtkPVFiltersCS.a ../../bin/libvtkPVFiltersPython.a ../../bin/libvtkPVServerManagerPython.a ../../bin/libvtkPVFiltersPythonD.a ../../bin/libvtkPVServerManagerPythonD.a ../../bin/libvtkPVFilters.a ../../bin/libvtkPVServerManager.a ../../bin/libvtkPVPythonInterpretor.a ../../bin/libvtkPVFiltersCS.a ../../bin/libvtkPVFiltersPython.a ../../bin/libvtkPVServerManagerPython.a ../../bin/libvtkPVFiltersPythonD.a ../../bin/libvtkPVServerManagerPythonD.a ../../bin/libicet_mpi.a ../../bin/libicet_strategies.a ../../bin/libicet.a ../../bin/libvtkXdmfCS.a ../../bin/libvtkXdmf.a ../../bin/libXdmf.a /lustre/scratch/proj/sw/pythoncnl/lib/libpython2.5.a ../../bin/libvtkCommonPython.a ../../bin/libvtkFilteringPython.a ../../bin/libvtkImagingPython.a ../../bin/libvtkGraphicsPython.a ../../bin/libvtkGenericFilteringPython.a ../../bin/libvtkGenericFilteringPythonD.a ../../bin/libvtkIOPython.a ../../bin/libvtkRenderingPython.a ../../bin/libvtkVolumeRenderingPython.a ../../bin/libvtkVolumeRenderingPythonD.a ../../bin/libvtkHybridPython.a ../../bin/libvtkWidgetsPython.a ../../bin/libvtkParallelPython.a ../../bin/libvtkInfovisPython.a ../../bin/libvtkGeovisPython.a ../../bin/libvtkGeovisPythonD.a ../../bin/libvtkGeovis.a ../../bin/libvtkproj4.a ../../bin/libvtkViewsPython.a ../../bin/libvtkChartsPython.a ../../bin/libvtkChartsPythonD.a ../../bin/libvtkViewsPythonD.a ../../bin/libvtkInfovisPythonD.a ../../bin/libvtkCharts.a ../../bin/libvtkViews.a
Re: [Paraview] static linking with python
On 03/03/2011 04:08 PM, Burlen Loring wrote: On 03/03/2011 05:39 AM, Brad King wrote: On 03/02/2011 06:31 PM, Burlen Loring wrote: Can anyone help figure out where these comes from and how to turn them off? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LINK_SEARCH_END_STATIC Thanks for the reply, I have been playing with this unsuccessfully. It doesn't have the desired effect so I think I'm doing something wrong. The documentation at that link gives the explanation of why Bdynamic appears: Make uses these options to set the link type for libraries whose full paths are not known or (in some cases) are in implicit link directories for the platform. By default the linker search type is left at -Bdynamic by the end of the library list. IOW any library of the form -lfoo is assumed to be -Bdynamic. Libraries in implicit link directories like /usr/lib/libbar.a will get turned into -Bstatic -lbar but then a later -lfoo will become -Bdynamic -lfoo since -lfoo is assumed to be dynamic. This is all because CMake assumes dynamic linking is preferred. The solution as of CMake 2.8.4 is to ensure that all libraries are given to target_link_libraries as full paths to the .a files so that CMake knows they are static. There is a TODO comment in the link computation code to support static linking: http://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmComputeLinkInformation.cxx;hb=v2.8.4#l820 I had been hoping to put in real support for a LINK_STATIC property that would work with all the generators in order to resolve that TODO comment. That is a lot of work though so it hasn't been done. I just added a minimal feature to CMake's development version to address the problem in this case: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5abfb571 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=077954d4 Now you can set a LINK_SEARCH_START_STATIC property to switch the dynamic linking assumption to static linking. In combination with -static that should produce a link line with no -Bdynamic options that links statically. This new feature should be available in the nightly builds by tomorrow: http://www.cmake.org/files/dev/?C=M;O=D -Brad ___ 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] static linking with python
On 03/02/2011 06:31 PM, Burlen Loring wrote: I'm trying to link paraview static and include python. In the executable link line there are a couple -Wl,-Bdynamic appearing and I am not able to locate their source. Can anyone help figure out where these comes from and how to turn them off? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LINK_SEARCH_END_STATIC -Brad ___ 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] static linking with python
On 03/03/2011 05:39 AM, Brad King wrote: On 03/02/2011 06:31 PM, Burlen Loring wrote: I'm trying to link paraview static and include python. In the executable link line there are a couple -Wl,-Bdynamic appearing and I am not able to locate their source. Can anyone help figure out where these comes from and how to turn them off? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LINK_SEARCH_END_STATIC -Brad Hi Brad, Thanks for the reply, I have been playing with this unsuccessfully. It doesn't have the desired effect so I think I'm doing something wrong. For each executable target I have gone into the relevant CMakeLists.txt and added a line like: set_target_properties(vtkpython pvtkpython PROPERTIES LINK_SEARCH_END_STATIC TRUE) but i still have -Wl,-Bdynamic in the link line (by the way I was playing with this yesterday, and the output in the initial post was with LINK_SEARCH_END_STATIC TRUE). A little more confusing is that when I set LINK_SEARCH_END_STATIC TRUE I get Bdynamic twice where as if it's set FALSE I only get it once. That's the opposite of what I would have expected. The new Bdynamic is appearing right after a Bstatic before the CMAKE_C_IMPLICIT_LINK_LIBRARIES. But neither case removes the Bdyamic that appears in the middle of the link line. I'm pasting the output from each of these below so you can see what I'm talking about. Burlen *LINK_SEARCH_END_STATIC FALSE* Linking CXX executable ../../../bin/vtkpython cd /global/homes/l/loring/Franklin/ParaView/PV3-3.8.1-py/VTK/Wrapping/Python /global/common/franklin/usg/cmake/2.8.2/bin/cmake -E cmake_link_script CMakeFiles/vtkpython.dir/link.txt --verbose=1 /opt/cray/xt-asyncpe/4.3/bin/CC-Wno-deprecated -Wno-deprecated -static -O3 -DNDEBUG -fPIC -Bstatic -static CMakeFiles/vtkpython.dir/vtkPythonAppInit.cxx.o -o ../../../bin/vtkpython -rdynamic -L/opt/fftw/3.2.2.1/lib/ -L/opt/cray/pmi/1.0-1..7901.22.1.ss/lib64 -L/opt/cray/mpt/5.1.3/xt/seastar/mpich2-gnu/lib -L/opt/cray/mpt/5.1.3/xt/seastar/sma/lib64 -L/opt/xt-libsci/10.5.0/gnu/lib/45 -L/opt/xt-libsci/10.5.0/gnu/lib -L/opt/xt-pe/2.2.48B/lib -L/opt/xt-pe/default/lib -L/opt/xt-pe/2.2.48B/lib/snos64 -L/opt/xt-pe/default/lib/snos64 -L/usr/lib/alps -L/opt/gcc/4.5.1/snos/lib/gcc/x86_64-suse-linux/4.5.1 -L/opt/gcc/4.5.1/snos/lib64 -L/lib64 -L/opt/gcc/4.5.1/snos/lib -lpthread /usr/common/graphics/python-cnl/2.7.1/lib/libpython2.7.a -lz ../../../bin/libvtksys.a ../../../bin/libvtkCommon.a ../../../bin/libvtkFiltering.a ../../../bin/libvtkIO.a ../../../bin/libvtkGraphics.a ../../../bin/libvtkImaging.a -Wl,-Bstatic -lutil ../../../bin/libvtkRendering.a ../../../bin/libvtkVolumeRendering.a ../../../bin/libvtkHybrid.a ../../../bin/libvtkWidgets.a ../../../bin/libvtkParallel.a ../../../bin/libvtkCharts.a ../../../bin/libvtkGeovis.a ../../../bin/libvtkInfovis.a ../../../bin/libvtkViews.a ../../../bin/libvtkCommonPython.a ../../../bin/libvtkFilteringPython.a ../../../bin/libvtkImagingPython.a ../../../bin/libvtkGraphicsPython.a ../../../bin/libvtkGenericFilteringPython.a ../../../bin/libvtkIOPython.a ../../../bin/libvtkRenderingPython.a ../../../bin/libvtkVolumeRenderingPython.a ../../../bin/libvtkHybridPython.a ../../../bin/libvtkWidgetsPython.a ../../../bin/libvtkParallelPython.a ../../../bin/libvtkInfovisPython.a ../../../bin/libvtkGeovisPython.a ../../../bin/libvtkViewsPython.a ../../../bin/libvtkChartsPython.a ../../../bin/libvtkGenericFilteringPythonD.a ../../../bin/libvtkGenericFiltering.a ../../../bin/libvtkVolumeRenderingPythonD.a ../../../bin/libvtkVolumeRendering.a ../../../bin/libvtkParallelPythonD.a ../../../bin/libvtkGeovisPythonD.a ../../../bin/libvtkGeovis.a ../../../bin/libvtkproj4.a ../../../bin/libvtkChartsPythonD.a ../../../bin/libvtkCharts.a ../../../bin/libvtkViewsPythonD.a ../../../bin/libvtkViews.a ../../../bin/libvtkInfovisPythonD.a ../../../bin/libvtkInfovis.a ../../../bin/libvtklibxml2.a -Wl,-Bdynamic -lm ../../../bin/libvtkalglib.a ../../../bin/libvtkWidgetsPythonD.a ../../../bin/libvtkWidgets.a ../../../bin/libvtkHybridPythonD.a ../../../bin/libvtkHybrid.a ../../../bin/libvtkParallel.a ../../../bin/libVPIC.a ../../../bin/libCosmo.a /opt/cray/mpt/5.1.0/xt/seastar/mpich2-gnu/lib/libmpich.a ../../../bin/libvtkexoIIc.a ../../../bin/libvtkIOPythonD.a ../../../bin/libvtkRenderingPythonD.a ../../../bin/libvtkRendering.a ../../../bin/libvtkIO.a ../../../bin/libvtkDICOMParser.a ../../../bin/libvtkNetCDF_cxx.a ../../../bin/libvtkNetCDF.a ../../../bin/libvtkmetaio.a ../../../bin/libvtksqlite.a ../../../bin/libvtkpng.a ../../../bin/libvtktiff.a ../../../bin/libvtkzlib.a ../../../bin/libvtkjpeg.a ../../../bin/libvtkexpat.a ../../../bin/libvtkftgl.a ../../../bin/libvtkfreetype.a /usr/common/graphics/ParaView/Mesa-7.5.1/lib64/libOSMesa.a ../../../bin/libvtkImagingPythonD.a ../../../bin/libvtkImaging.a ../../../bin/libvtkGraphicsPythonD.a ../../../bin/libvtkGraphics.a
Re: [Paraview] static linking with python
Brad I can demonstrate this here... David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Thu, Mar 3, 2011 at 4:08 PM, Burlen Loring blor...@lbl.gov wrote: On 03/03/2011 05:39 AM, Brad King wrote: On 03/02/2011 06:31 PM, Burlen Loring wrote: I'm trying to link paraview static and include python. In the executable link line there are a couple -Wl,-Bdynamic appearing and I am not able to locate their source. Can anyone help figure out where these comes from and how to turn them off? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:LINK_SEARCH_END_STATIC -Brad Hi Brad, Thanks for the reply, I have been playing with this unsuccessfully. It doesn't have the desired effect so I think I'm doing something wrong. For each executable target I have gone into the relevant CMakeLists.txt and added a line like: set_target_properties(vtkpython pvtkpython PROPERTIES LINK_SEARCH_END_STATIC TRUE) but i still have -Wl,-Bdynamic in the link line (by the way I was playing with this yesterday, and the output in the initial post was with LINK_SEARCH_END_STATIC TRUE). A little more confusing is that when I set LINK_SEARCH_END_STATIC TRUE I get Bdynamic twice where as if it's set FALSE I only get it once. That's the opposite of what I would have expected. The new Bdynamic is appearing right after a Bstatic before the CMAKE_C_IMPLICIT_LINK_LIBRARIES. But neither case removes the Bdyamic that appears in the middle of the link line. I'm pasting the output from each of these below so you can see what I'm talking about. Burlen LINK_SEARCH_END_STATIC FALSE Linking CXX executable ../../../bin/vtkpython cd /global/homes/l/loring/Franklin/ParaView/PV3-3.8.1-py/VTK/Wrapping/Python /global/common/franklin/usg/cmake/2.8.2/bin/cmake -E cmake_link_script CMakeFiles/vtkpython.dir/link.txt --verbose=1 /opt/cray/xt-asyncpe/4.3/bin/CC -Wno-deprecated -Wno-deprecated -static -O3 -DNDEBUG -fPIC -Bstatic -static CMakeFiles/vtkpython.dir/vtkPythonAppInit.cxx.o -o ../../../bin/vtkpython -rdynamic -L/opt/fftw/3.2.2.1/lib/ -L/opt/cray/pmi/1.0-1..7901.22.1.ss/lib64 -L/opt/cray/mpt/5.1.3/xt/seastar/mpich2-gnu/lib -L/opt/cray/mpt/5.1.3/xt/seastar/sma/lib64 -L/opt/xt-libsci/10.5.0/gnu/lib/45 -L/opt/xt-libsci/10.5.0/gnu/lib -L/opt/xt-pe/2.2.48B/lib -L/opt/xt-pe/default/lib -L/opt/xt-pe/2.2.48B/lib/snos64 -L/opt/xt-pe/default/lib/snos64 -L/usr/lib/alps -L/opt/gcc/4.5.1/snos/lib/gcc/x86_64-suse-linux/4.5.1 -L/opt/gcc/4.5.1/snos/lib64 -L/lib64 -L/opt/gcc/4.5.1/snos/lib -lpthread /usr/common/graphics/python-cnl/2.7.1/lib/libpython2.7.a -lz ../../../bin/libvtksys.a ../../../bin/libvtkCommon.a ../../../bin/libvtkFiltering.a ../../../bin/libvtkIO.a ../../../bin/libvtkGraphics.a ../../../bin/libvtkImaging.a -Wl,-Bstatic -lutil ../../../bin/libvtkRendering.a ../../../bin/libvtkVolumeRendering.a ../../../bin/libvtkHybrid.a ../../../bin/libvtkWidgets.a ../../../bin/libvtkParallel.a ../../../bin/libvtkCharts.a ../../../bin/libvtkGeovis.a ../../../bin/libvtkInfovis.a ../../../bin/libvtkViews.a ../../../bin/libvtkCommonPython.a ../../../bin/libvtkFilteringPython.a ../../../bin/libvtkImagingPython.a ../../../bin/libvtkGraphicsPython.a ../../../bin/libvtkGenericFilteringPython.a ../../../bin/libvtkIOPython.a ../../../bin/libvtkRenderingPython.a ../../../bin/libvtkVolumeRenderingPython.a ../../../bin/libvtkHybridPython.a ../../../bin/libvtkWidgetsPython.a ../../../bin/libvtkParallelPython.a ../../../bin/libvtkInfovisPython.a ../../../bin/libvtkGeovisPython.a ../../../bin/libvtkViewsPython.a ../../../bin/libvtkChartsPython.a ../../../bin/libvtkGenericFilteringPythonD.a ../../../bin/libvtkGenericFiltering.a ../../../bin/libvtkVolumeRenderingPythonD.a ../../../bin/libvtkVolumeRendering.a ../../../bin/libvtkParallelPythonD.a ../../../bin/libvtkGeovisPythonD.a ../../../bin/libvtkGeovis.a ../../../bin/libvtkproj4.a ../../../bin/libvtkChartsPythonD.a ../../../bin/libvtkCharts.a ../../../bin/libvtkViewsPythonD.a ../../../bin/libvtkViews.a ../../../bin/libvtkInfovisPythonD.a ../../../bin/libvtkInfovis.a ../../../bin/libvtklibxml2.a -Wl,-Bdynamic -lm ../../../bin/libvtkalglib.a ../../../bin/libvtkWidgetsPythonD.a ../../../bin/libvtkWidgets.a ../../../bin/libvtkHybridPythonD.a ../../../bin/libvtkHybrid.a ../../../bin/libvtkParallel.a ../../../bin/libVPIC.a ../../../bin/libCosmo.a /opt/cray/mpt/5.1.0/xt/seastar/mpich2-gnu/lib/libmpich.a ../../../bin/libvtkexoIIc.a ../../../bin/libvtkIOPythonD.a ../../../bin/libvtkRenderingPythonD.a ../../../bin/libvtkRendering.a ../../../bin/libvtkIO.a ../../../bin/libvtkDICOMParser.a ../../../bin/libvtkNetCDF_cxx.a ../../../bin/libvtkNetCDF.a ../../../bin/libvtkmetaio.a ../../../bin/libvtksqlite.a ../../../bin/libvtkpng.a ../../../bin/libvtktiff.a ../../../bin/libvtkzlib.a ../../../bin/libvtkjpeg.a ../../../bin/libvtkexpat.a ../../../bin/libvtkftgl.a
[Paraview] static linking with python
Hi, I'm trying to link paraview static and include python. In the executable link line there are a couple -Wl,-Bdynamic appearing and I am not able to locate their source. Can anyone help figure out where these comes from and how to turn them off? Burlen Linking CXX executable ../../bin/pvserver cd /global/homes/l/loring/Franklin/ParaView/PV3-3.8.1-py/Servers/Executables /global/common/franklin/usg/cmake/2.8.2/bin/cmake -E cmake_link_script CMakeFiles/pvserver.dir/link.txt --verbose=1 /opt/cray/xt-asyncpe/4.3/bin/CC-Wno-deprecated -static -O3 -DNDEBUG -fPIC -Bstatic -static CMakeFiles/pvserver.dir/pvserver.cxx.o -o ../../bin/pvserver -rdynamic -L/opt/fftw/3.2.2.1/lib/ -L/opt/cray/pmi/1.0-1..7901.22.1.ss/lib64 -L/opt/cray/mpt/5.1.3/xt/seastar/mpich2-gnu/lib -L/opt/cray/mpt/5.1.3/xt/seastar/sma/lib64 -L/opt/xt-libsci/10.5.0/gnu/lib/45 -L/opt/xt-libsci/10.5.0/gnu/lib -L/opt/xt-pe/2.2.48B/lib -L/opt/xt-pe/default/lib -L/opt/xt-pe/2.2.48B/lib/snos64 -L/opt/xt-pe/default/lib/snos64 -L/usr/lib/alps -L/opt/gcc/4.5.1/snos/lib/gcc/x86_64-suse-linux/4.5.1 -L/opt/gcc/4.5.1/snos/lib64 -L/lib64 -L/opt/gcc/4.5.1/snos/lib ../../bin/libvtkPVServerCommon.a ../../bin/libvtkPVFilters.a ../../bin/libvtkPVServerManager.a ../../bin/libvtkPVPythonInterpretor.a ../../bin/libvtkPVFiltersCS.a ../../bin/libvtkPVFiltersPython.a ../../bin/libvtkPVServerManagerPython.a ../../bin/libvtkPVFiltersPythonD.a ../../bin/libvtkPVServerManagerPythonD.a ../../bin/libvtkPVFilters.a ../../bin/libvtkPVServerManager.a ../../bin/libvtkPVPythonInterpretor.a ../../bin/libvtkPVFiltersCS.a ../../bin/libvtkPVFiltersPython.a ../../bin/libvtkPVServerManagerPython.a ../../bin/libvtkPVFiltersPythonD.a ../../bin/libvtkPVServerManagerPythonD.a ../../bin/libicet_mpi.a ../../bin/libicet_strategies.a ../../bin/libicet.a ../../bin/libvtkXdmfCS.a ../../bin/libvtkXdmf.a ../../bin/libXdmf.a /usr/common/graphics/python-cnl/2.7.1/lib/libpython2.7.a ../../bin/libvtkCommonPython.a ../../bin/libvtkFilteringPython.a ../../bin/libvtkImagingPython.a ../../bin/libvtkGraphicsPython.a ../../bin/libvtkGenericFilteringPython.a ../../bin/libvtkGenericFilteringPythonD.a ../../bin/libvtkIOPython.a ../../bin/libvtkRenderingPython.a ../../bin/libvtkVolumeRenderingPython.a ../../bin/libvtkVolumeRenderingPythonD.a ../../bin/libvtkHybridPython.a ../../bin/libvtkWidgetsPython.a ../../bin/libvtkParallelPython.a ../../bin/libvtkInfovisPython.a ../../bin/libvtkGeovisPython.a ../../bin/libvtkGeovisPythonD.a ../../bin/libvtkGeovis.a ../../bin/libvtkproj4.a ../../bin/libvtkViewsPython.a ../../bin/libvtkChartsPython.a ../../bin/libvtkChartsPythonD.a ../../bin/libvtkViewsPythonD.a ../../bin/libvtkInfovisPythonD.a ../../bin/libvtkCharts.a ../../bin/libvtkViews.a ../../bin/libvtkPVServerCommonPython.a -lz -Wl,-Bstatic -lutil ../../bin/libvtkVolumeRenderingCS.a ../../bin/libvtkVolumeRendering.a ../../bin/libvtkWidgetsCS.a ../../bin/libvtkWidgetsPythonD.a ../../bin/libvtkHybridPythonD.a ../../bin/libvtkParallelPythonD.a ../../bin/libvtkRenderingPythonD.a ../../bin/libvtkImagingPythonD.a ../../bin/libvtkGraphicsPythonD.a ../../bin/libvtkPVServerCommonPythonD.a ../../bin/libvtkPVServerCommonCS.a ../../bin/libvtkPVServerCommon.a ../../bin/libvtkInfovisCS.a ../../bin/libvtkInfovis.a ../../bin/libvtkWidgets.a ../../bin/libvtklibxml2.a ../../bin/libvtkalglib.a ../../bin/libKWCommon.a ../../bin/libhdf5.a -Wl,-Bdynamic -lm ../../bin/libvtkPVCommandOptions.a ../../bin/libvtkHybridCS.a ../../bin/libvtkHybrid.a ../../bin/libvtkParallelCS.a ../../bin/libvtkParallel.a ../../bin/libvtkexoIIc.a ../../bin/libVPIC.a ../../bin/libCosmo.a /opt/cray/mpt/5.1.0/xt/seastar/mpich2-gnu/lib/libmpich.a ../../bin/libvtkRenderingCS.a ../../bin/libvtkRendering.a /usr/common/graphics/ParaView/Mesa-7.5.1/lib64/libOSMesa.a ../../bin/libvtkftgl.a ../../bin/libvtkfreetype.a ../../bin/libvtkGenericFilteringCS.a ../../bin/libvtkGenericFiltering.a ../../bin/libvtkGraphicsCS.a ../../bin/libvtkGraphics.a ../../bin/libvtkverdict.a ../../bin/libvtkImagingCS.a ../../bin/libvtkImaging.a ../../bin/libvtkIOCS.a ../../bin/libvtkFilteringCS.a ../../bin/libvtkCommonCS.a ../../bin/libvtkClientServer.a ../../bin/libvtkIOPythonD.a ../../bin/libvtkIO.a ../../bin/libvtkDICOMParser.a ../../bin/libvtkNetCDF_cxx.a ../../bin/libvtkNetCDF.a ../../bin/libvtkmetaio.a ../../bin/libvtksqlite.a ../../bin/libvtkpng.a ../../bin/libvtktiff.a ../../bin/libvtkzlib.a ../../bin/libvtkjpeg.a ../../bin/libvtkexpat.a ../../bin/libvtkFilteringPythonD.a ../../bin/libvtkFiltering.a ../../bin/libvtkCommonPythonD.a ../../bin/libvtkCommon.a ../../bin/libvtksys.a -ldl -lm -lpthread -Wl,-Bstatic -Wl,-Bdynamic -lmpich -lrt -lsma -lportals -lpmi -lalpslli -lalpsutil -lm -lc -lc_p -lpthread -lfftw3 -lfftw3f ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep
