Package Details: paraview-opt 5.9.0-1

Git Clone URL: (read-only, click to copy)
Package Base: paraview-opt
Description: Parallel Visualization application using VTK (openmpi version): installed to /opt/
Upstream URL:
Licenses: custom, BSD
Conflicts: paraview
Provides: paraview
Submitter: bartus
Maintainer: bartus (Archange)
Last Packager: Archange
Votes: 9
Popularity: 0.022448
First Submitted: 2019-04-25 09:44
Last Updated: 2021-03-20 11:28

Dependencies (45)

Required by (8)

Sources (2)

Pinned Comments

bartus commented on 2020-02-20 23:06

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

1 2 3 4 5 6 ... Next › Last »

bartus commented on 2020-12-12 07:51

@kikislater: Yep, that's a good point. I'm also using both Manjaro and Arch interchangeably (ง ื▿ ื)ว

Archange commented on 2020-12-06 18:43

@lahwaacz True, but the same way we have some arm architectures support in AUR PKGBUILD, it does not hurt to not block Manjaro.

For instance, the “official” patch could have been used (and I’ll push it here later when I can). Keeping both packages as much as possible in sync seems a good idea to me.

kikislater commented on 2020-12-06 18:40

It's not a hack ^^ Just a suggestion ...

lahwaacz commented on 2020-12-06 18:20

@kikislater This is the Arch User Repository, not Manjaro User Repository. There should be no such hacks.

kikislater commented on 2020-12-06 17:51

@bartus : it's ok on mate desktop, thank you

One thing is that others distribution such as Manjaro rely on AUR packages. Stable version of Manjaro is still on python 3.8 but will move shortly to 3.9. One more elegant way in PKGBUILD should be to detect with an if statement which python is used like :

ver=$(python -V 2>&1 | sed 's/.* \([0-9]\).\([0-9]\).*/\1\2/')
if [ "$ver" -lt "39" ]; then echo 
"Patching Paraview to work with Python 3.9"; 
    # add python:3.9
    sed -i "s|3.8|3.9 &|" VTK/CMake/patches/99/FindPython/Support.cmake;
echo "You use Python 3.8, no modification needed";

bartus commented on 2020-12-04 09:08

@kikislater: I've adjusted the PKGBUILD to expose desktop file and icons d8621eea5aa1 , please test how it's doing (it relays on /etc/profile.d/ exporting PATH with included /opt/paraview/bin)

@Xwang, @jemappelle: I've added python:3.9 support 5f21b9bea9c7

jemappelle commented on 2020-12-02 20:03

@Xwang: Thanks a lot for the information cause I had the same issue thus I tried compiling it with the patch available in the official package as you mentioned it and it worked like a charm.

Xwang commented on 2020-12-02 11:36

I can't compile.It gives the following configuration error:

-- Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS Development) (Required is at least version "3.2")
CMake Error at VTK/CMake/vtkModule.cmake:4112 (message):
  Could not find the Python3 external dependency.
Call Stack (most recent call first):
  VTK/Utilities/Python/CMakeLists.txt:44 (vtk_module_find_package)

-- Configuring incomplete, errors occurred!
See also "/home/andreak/tmp/pamac-andreak/pamac-build/paraview-opt/src/build/CMakeFiles/CMakeOutput.log".
See also "/home/andreak/tmp/pamac-andreak/pamac-build/paraview-opt/src/build/CMakeFiles/CMakeError.log".
==> ERRORE: Si è verificato un errore in build().

In the officila package there is a python39 patch which probably solves the issue:

kikislater commented on 2020-10-19 10:45

Thank you bartus providing this package making freecad, openfoam and paraview working together ! As no .desktop is not provided in /usr/share and no symlink of paraview in /usr/bin or /usr/local/bin, paraview is not available in menu. I think it could be nice for users, as paraview is a gui, to add symlink in this package !

Archange commented on 2020-10-15 16:09

@bartus: Well it looks strange, because in the [community] package the checksum had to be changed to 9760a7ba33c6f46e3cb8dc8d0e2370ee1208d759b3c8c6c304e7e4b366391a13.

Have you tried re-downloading the patch too? They are some small differences in the indexes that result in this checksum difference.