Install paraview-3.98 with the development use flag enabled. Then run: freddie@fluorine ~/Programming/PyFR $ grep "/var/tmp" /usr/lib64/cmake/paraview-3.98/* grep: /usr/lib64/cmake/paraview-3.98/Modules: Is a directory /usr/lib64/cmake/paraview-3.98/ParaViewConfig.cmake: set (VTK_CONFIG_FILE "/var/tmp/portage/sci-visualization/paraview-3.98.0-r1/work/paraview-3.98.0_build/VTK/VTKConfig.cmake") /usr/lib64/cmake/paraview-3.98/ParaViewConfig.cmake: set (ParaView_CMAKE_DIR "/var/tmp/portage/sci-visualization/paraview-3.98.0-r1/work/ParaView-3.98.0-src/CMake") /usr/lib64/cmake/paraview-3.98/ParaViewConfig.cmake: set (PARAVIEW_CONFIG_TARGETS_FILE "/var/tmp/portage/sci-visualization/paraview-3.98.0-r1/work/paraview-3.98.0_build/ParaViewTargets.cmake") /usr/lib64/cmake/paraview-3.98/ParaViewConfig.cmake: list(APPEND VTK_INCLUDE_DIRS "/var/tmp/portage/sci-visualization/paraview-3.98.0-r1/work/paraview-3.98.0_build") /usr/lib64/cmake/paraview-3.98/VTKConfig.cmake:include("/var/tmp/portage/sci-visualization/paraview-3.98.0-r1/work/ParaView-3.98.0-src/VTK/CMake/vtkTestingMacros.cmake") Observe how several of the cmake configuration files reference /var/tmp. This creates a range of issues when attempting to use these cmake files to build plugins for paraview. (As they in turn attempt to include from /var/tmp/...).
Do you have an idea how to fix it? I might not have time to look deeper into that in the next few days. Paraview build system is one of the biggest I know of...
any change for paraview-4.0.1?
This appears to be fixed with ParaView 4.0.