Package Details: paraview-opt 5.8.0-4

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: bartus
Votes: 6
Popularity: 1.56
First Submitted: 2019-04-25 09:44
Last Updated: 2020-05-08 07:16

Dependencies (43)

Required by (10)

Sources (3)

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 Next › Last »

ccorn commented on 2020-05-08 10:18

@bartus: Thanks for the Archwiki CMake and C*FLAGS reference!

bartus commented on 2020-05-08 07:15

@ccron: thanks for the tip, I've unjustifiably assumed that [commumity/paraview] packager has it covered when using this syntax.

I've also had no idea that CPPFLAGS is such problem that it's mentioned in Archwiki :(

ccorn commented on 2020-05-08 06:09

Note that the -DCMAKE_CXX_FLAGS="-DH5_USE_110_API" makes CMake ignore the build environment's CXXFLAGS, which is why I have proposed appending to the environment variables instead. Cf. bug report #66441. The practical effects of this ignorance are minor because you still get a release build with options chosen by CMake, but generally I'd like to see the settings in makepkg.conf respected. All of them.

It gets worse. The CMake docs do not mention CPPFLAGS at all, so that variable always gets ignored by CMake. Therefore, ideally we should begin build() with

CPPFLAGS+=" -DH5_USE_110_API"  # space before -D needed
# ...
cmake ... \

where the mentioned cmake commandline fragment should be used in every CMake-based PKGBUILD. This way, the environment keeps following GNU autoconf standards, and CMake still gets all the tweaks set in makepkg.conf (which usually includes -D_FORTIFY_SOURCE=2 in CPPFLAGS, -fno-plt in C*FLAGS and more secure LDFLAGS).

ccorn commented on 2020-05-08 05:12

@irrianlo: The last part of that upstream patch file (outside the sections used by patch) contains a git version number which regularly changes. I suggest checking in a fixed copy of the patch to stabilize the checksum.

irrianlo commented on 2020-05-02 23:35

while downloading paraview-cgns-4.1.patch appears an error of shasum validaton.

==> Validating source files with sha256sums... ParaView-v5.8.0.tar.xz ... Passed paraview-cgns-4.1.patch ... FAILED ... Passed ==> ERROR: One or more files did not pass the validity check! Error downloading sources: paraview-opt

ccorn commented on 2020-04-28 05:30

The recent hdf5 upgrade requires compatibility settings for Paraview-5.8.0. Begin build() with the following:

    # H5Oget_info_by_name, H5Oget_info have changed prototypes in HDF5 1.12
    CXXFLAGS+=" -DH5_USE_110_API"
    CFLAGS+=" -DH5_USE_110_API"

hottea commented on 2020-04-07 11:46

why in deps? I can't upgrade my system due to dep issue related to jsoncpp.

paraview-opt depends on

bartus commented on 2020-02-29 13:04

@boomboompsh: Yep, building paraview is a pain - one suggestion I might have, enable option=(ccache) to speed up the rebuild, at least until next gcc version appears.

boomboompsh commented on 2020-02-28 17:53

@bartus Oh. I assumed 1G per core would be enough. would be really nice if OOM errors produced OOM messages instead of something about EOFs in assembly files. Well, I installed a binary version so I probably won't spend another 8 hours recompiling, but good to know.

bartus commented on 2020-02-28 16:29

@boomboompsh: check out the pined comment Basically, there isn't enough memory per core to link the project.