Arch Linux User Repository

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

I have the same issue as @Xwang and @net147 but in the meanwhile, just build the version directly from paraview: https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md

I have the same issue as net147

This is the output of sha256sum paraview-cgns-4.1.patch:

917485fbff57b922e67e40ee35d265769b05b4b62c397e4c9ce00244f5fd07ae paraview-cgns-4.1.patch

which differs from the value in the PKGBUILD

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

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

@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 :(

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 ... \
-DCMAKE_C_FLAGS="$CPPFLAGS $CFLAGS" \
-DCMAKE_CXX_FLAGS="$CPPFLAGS $CXXFLAGS"

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).

@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.

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 paraview.sh ... Passed ==> ERROR: One or more files did not pass the validity check! Error downloading sources: paraview-opt

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"
    export CFLAGS CXXFLAGS

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

paraview-opt depends on libjsoncpp.so=21-64