From RDEPEND in paraview-4.2.0-r1.ebuild: ``` python? ( ${PYTHON_DEPS} dev-python/matplotlib[${PYTHON_USEDEP}] dev-python/mpi4py dev-python/numpy[${PYTHON_USEDEP}] dev-python/sip[${PYTHON_USEDEP}] dev-python/twisted-core dev-python/zope-interface[${PYTHON_USEDEP}] mpi? ( dev-python/mpi4py ) qt4? ( dev-python/PyQt4[opengl,webkit,${PYTHON_USEDEP}] ) ) ``` Note that mpi4py appears twice: once in a mpi? bracket and once outside Reproducible: Always
The same problem exists in the 4.0.1 and 4.1.0 ebuilds. Also, presumably there are some ${PYTHON_USEDEP}s missing.
Another problem I spotted - zope.interface should be net-zope/zope.interface rather than dev-python/zope-interface (I'm not sure about this, just guessing)
I've tried building paraview with various options First I tried: USE="-python -mpi" emerge --onlydeps paraview USE="python -mpi" emerge --nodeps paraview This fails in src_configure with the following error: ``` CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: MPI_C_LIBRARIES (ADVANCED) linked by target "pmpi-vt" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py linked by target "pmpi-mpe" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py linked by target "pmpi-vt-hyb" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py linked by target "mpi4py.MPE" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py linked by target "mpi4py.MPI" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py linked by target "pmpi-vt-mpi" in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py MPI_HEADER_PATH used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/VTK/ThirdParty/mpi4py/vtkmpi4py used as include directory in directory /var/tmp/portage/sci-visualization/paraview-4.2.0-r1/work/ParaView-v4.2.0-source/Plugins/SciberQuestToolKit/ParaViewPlugin ``` Hopefully it should be possible to disable this 'third party' component if either python or mpi are not in USE. If not then there should be something in REQUIRED_USE.
*paraview-4.3.1 (19 Apr 2015) 19 Apr 2015; Matthias Maier <tamiko@gentoo.org> +files/paraview-4.1.0-vtk-freetype.patch, +files/paraview-4.2.0-protobuf-2.patch, +files/paraview-4.2.0-protobuf.patch, +paraview-4.3.1.ebuild, -files/paraview-4.2.0-Protobuf.patch, -paraview-4.0.1-r2.ebuild, paraview-4.1.0-r2.ebuild, paraview-4.2.0-r1.ebuild: version bump (bug #538690), fix dependencies (bug #538168), fix freetype-2.5.5 compatibility also in 4.1.0-r2 (bug #541012), fix protobuf compatibility in 4.2.0 and 4.3.1 (bug #537988) (In reply to Chris Kerr from comment #0) > From RDEPEND in paraview-4.2.0-r1.ebuild: > ``` > python? ( > ${PYTHON_DEPS} > dev-python/matplotlib[${PYTHON_USEDEP}] > dev-python/mpi4py > dev-python/numpy[${PYTHON_USEDEP}] > dev-python/sip[${PYTHON_USEDEP}] > dev-python/twisted-core > dev-python/zope-interface[${PYTHON_USEDEP}] > mpi? ( dev-python/mpi4py ) > qt4? ( dev-python/PyQt4[opengl,webkit,${PYTHON_USEDEP}] ) > ) > ``` I (hopefully) fixed the dependencies. Unfortunately, I'm not able to reproduce your configuration failures. Please also attach an emerge --info.
