Package Details: paraview-git v5.8.1.RC1.r819.g08210ebaca-1

Git Clone URL: https://aur.archlinux.org/paraview-git.git (read-only, click to copy)
Package Base: paraview-git
Description: Open-source, multi-platform data analysis and visualization application
Upstream URL: https://www.paraview.org
Licenses: custom, BSD
Conflicts: paraview, vtk
Provides: paraview
Submitter: GloW
Maintainer: GloW
Last Packager: GloW
Votes: 3
Popularity: 0.037263
First Submitted: 2017-09-25 09:46 (UTC)
Last Updated: 2020-06-22 10:15 (UTC)

Required by (8)

Sources (1)

Pinned Comments

GloW commented on 2020-06-22 10:18 (UTC) (edited on 2020-06-22 10:23 (UTC) by GloW)

Out of memory error.

You may use ninja-mem to prevent trashing when building on system with low memory to core ratio.

To activate use MAKEFLAGS+=" -m75" where 75 is the percent of memory usage when trashing prevention kicks in.

Or simply lower the make parallel jobs in "MAKEFLAGS" variable.

Refers to #731427 #716760

Latest Comments

xantares commented on 2021-08-30 15:25 (UTC)

it needs exprtk-git, cli11 and fmt third party dependencies

SandFloh commented on 2021-07-09 07:31 (UTC)

Thank you for providing this.

I had to install cl11, maybe you should add it to the dependencies: https://aur.archlinux.org/packages/cli11/

I also had to disable the use of the system PEGTL with the command "-DVTK_MODULE_USE_EXTERNAL_VTK_pegtl=OFF". Here is more information about it: https://gitlab.kitware.com/vtk/vtk/-/issues/18151

massisenergy commented on 2020-07-27 17:35 (UTC) (edited on 2020-07-27 17:36 (UTC) by massisenergy)

It fails in Manjaro, like this (only the last few lines):

.
.
.
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found GLEW: /usr/lib/libGLEW.so  
-- Found Eigen3: /usr/include/eigen3 (found version "3.3.7") 
-- Found MPI_C: /usr/lib/openmpi/libmpi.so (found version "3.1") 
-- Found MPI: TRUE (found version "3.1") found components: C 
CMake Warning at VTK/CMake/vtkModule.cmake:4160 (find_package):
  Could not find a configuration file for package "ospray" that is compatible
  with requested version "2.1".

  The following configuration files were considered but not accepted:

    /usr/lib64/cmake/ospray-1.8.5/osprayConfig.cmake, version: 1.8.5
    /usr/lib/cmake/ospray-1.8.5/osprayConfig.cmake, version: 1.8.5
    /lib64/cmake/ospray-1.8.5/osprayConfig.cmake, version: 1.8.5
    /lib/cmake/ospray-1.8.5/osprayConfig.cmake, version: 1.8.5

Call Stack (most recent call first):
  VTK/Rendering/RayTracing/CMakeLists.txt:62 (vtk_module_find_package)


CMake Error at VTK/CMake/vtkModule.cmake:4166 (message):
  Could not find the ospray external dependency.
Call Stack (most recent call first):
  VTK/Rendering/RayTracing/CMakeLists.txt:62 (vtk_module_find_package)


-- Configuring incomplete, errors occurred!
See also "/home/msr/.cache/yay/paraview-git/src/build/CMakeFiles/CMakeOutput.log".
See also "/home/msr/.cache/yay/paraview-git/src/build/CMakeFiles/CMakeError.log".
==> ERROR: A failure occurred in build().
    Aborting...
error making: %!s(func() string=0x5622f57c0830)

GloW commented on 2020-06-22 10:18 (UTC) (edited on 2020-06-22 10:23 (UTC) by GloW)

Out of memory error.

You may use ninja-mem to prevent trashing when building on system with low memory to core ratio.

To activate use MAKEFLAGS+=" -m75" where 75 is the percent of memory usage when trashing prevention kicks in.

Or simply lower the make parallel jobs in "MAKEFLAGS" variable.

Refers to #731427 #716760

GloW commented on 2020-06-22 10:17 (UTC)

@hacksd : I can't reproduce your issue.

GloW commented on 2020-06-22 10:17 (UTC)

@InspiringSand : Thanks for your valuable input, i've taken all your comment into accounts.

hacksd commented on 2020-06-01 22:24 (UTC) (edited on 2020-06-01 22:26 (UTC) by hacksd)

I am getting this error when trying to build this package:

CMake Error at CMakeLists.txt:330 (message): The following modules were requested or required, but not found: ParaView::IOVisItBridge;ParaView::VisItLib.

These are not in gitmodules.

InspiringSand commented on 2020-05-26 11:54 (UTC) (edited on 2020-05-27 14:47 (UTC) by InspiringSand)

I ran into some issues:

  • pegtl is not listed as a makedependency and this throws an error if the package is not installed. After installing pegtl explicitly, this wasn't an issue anymore.
  • Then two subsequent builds (8 cores, 16 threads, 16 GB RAM) a failure would occure.
    ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting...
    Rebooting and running with no RAM in use by other programs fixed this. I kept an eye on memory usage during this build. It stayed within 4-6GB for the first 30-40%, but spiked to 15GB around the point where it aborted the first two times (9000-10000/20000). Consider pinning a comment like the one in paraview-opt here as well: https://aur.archlinux.org/packages/paraview-opt/
  • So the third build seemed to finish, but I got vtk conflicts at the very end, so it didn't complete after all. Example:
    paraview-git: /usr/lib/python3.8/site-packages/vtk.py already exists in filesystem (owned by vtk)
    I have vtk installed as a dependency of gmsh.
    The community package paraview lists vtk as a conflict. Could you add that as well?
    Additional links:
    https://gitlab.kitware.com/paraview/paraview/issues/18751
    https://bugs.archlinux.org/task/61594
  • @hottea: paraview-opt uses that directory intentionally as a workaround for the vtk conflict. I'm trying to figure out what the easiest way is for me to solve this if I wanna build the latest version. Would changing -DCMAKE_INSTALL_PREFIX=/usr \ to -DCMAKE_INSTALL_PREFIX=/opt/paraview \ work? Also if I do this I think I'll need to add paraview to PATH as is done at the end of the PKGBUILD file for paraview-opt. Thoughts?
  • Furthermore I noticed paraview-opt uses -DVTK_MODULE_ENABLE_VTK_IOGDAL=YES \ and -DVTK_MODULE_ENABLE_VTK_IOPDAL=YES \ which is discussed here if you want to look into it: https://discourse.vtk.org/t/vtkiogdal-and-vtkiogeojson/103, but I'm not sure it's relevant. Just comparing both build files.

GloW commented on 2020-02-20 10:27 (UTC)

@Archange : Thanks, I've updated the package.

Archange commented on 2020-02-18 18:35 (UTC)

@gpettinello: You’re issue has been fixed upstream.

@GloW: There has been some changes, qt5-svg is a new dependency, DPARAVIEW_USE_PYTHON=ON replaced DPARAVIEW_ENABLE_PYTHON=ON, system pugixml can now be used and there has been a nice simplification in using system dependencies in general: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/paraview&id=701484f3e63e010eeb229315761bc2d12f11f562.

hottea commented on 2019-12-20 02:04 (UTC)

@GloW I'm so sorry. I mean the paraview-opt pkg, not paraview-git.

GloW commented on 2019-12-19 14:26 (UTC) (edited on 2019-12-19 14:26 (UTC) by GloW)

$ pacman -Ql paraview-git | grep desktop
paraview-git /usr/share/applications/org.paraview.ParaView.desktop

Nothing is installed in /opt/

hottea commented on 2019-12-19 14:18 (UTC)

The desktop file is installed to /opt/paraview/share/applications/org.paraview.ParaView.desktop. This is not a proper place. GNOME could not find paraview. We should install it to /usr/share/applications. And the icon image should be installed to proper location too. We cannot simply install everything to /opt.

GloW commented on 2019-11-25 16:17 (UTC)

Do you have a specific version of MPI installed on your system ?

gpettinello commented on 2019-11-17 12:15 (UTC)

Error in compilation which is the same as paraview official package: conflicting symbol MPI_Comm

GloW commented on 2019-11-11 17:17 (UTC)

@xantares @Kunda Package have been updated.

GloW commented on 2019-11-11 11:05 (UTC)

@JoshH100 I'm afraid linking all submdule in the source array is not a good idea has the number of submodules can actually change over time, hence breaking the package.

GloW commented on 2019-11-10 14:43 (UTC)

Sorry for the delay. ParaView changed a lot this year, I will update soon.

xantares commented on 2019-11-07 19:38 (UTC)

VTK_USE_SYSTEM_XX is not used anymore, use PARAVIEW_USE_EXTERNAL=ON and VTK_MODULE_USE_EXTERNAL_VTK_gl2ps=OFF

Kunda commented on 2019-10-15 12:49 (UTC)

@GloW do you mind bumping the package number to 5.7.0.xxxx

PrinceMachiavell commented on 2019-05-29 09:41 (UTC)

I seem to always get some error while at the Vtkm compilation stage. I've tried adjust the parameters set by the for loops to what the arch paraview & VTK packages use (they are different) but neither seems to work.

[14334/18859] Running cpp protocol buffer compiler on vtkPVMessage.proto FAILED: ParaViewCore/ServerImplementation/Core/vtkPVMessage.pb.h ParaViewCore/ServerImplementation/Core/vtkPVMessage.pb.cc cd /data/paraview_org/paraview-git/src/build/ParaViewCore/ServerImplementation/Core && /data/paraview_org/paraview git/src/build/bin/vtkprotoc-pv5.6 --cpp_out dllexport_decl=VTKPVSERVERIMPLEMENTATIONCORE_EXPORT:/data/paraview_org/paraview-git/src/build/ParaViewCore/ServerImplementation/Core -I /data/paraview_org/paraview-git/src/paraview/ParaViewCore/ServerImplementation/Core /data/paraview_org/paraview-git/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPVMessage.proto terminate called after throwing an instance of 'std::system_error'

I've attempted to use the paraview nightly binaries but it appears that some part of it is compiled against an old fontconfig version which makes the 'paraview' executable impossible to use even with redirected library versions.

Also, it would be a good idea to incorporate the submodules into the sources array and reference them in prepare() rather than have to download them every time.

I maintaine (sort of) similar software suits that have similar systemic build issues so to be clear I'm not pestering the maintainer to fix the issue, I mearly want to document my experience and recomendations.