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

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 !

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

I've installed it again with pamac with no issue and the checksum is correct. Problem solved. Thank you!

@lahwaacz: fixed 7361d65e0445

@Xwang, @jemappelle: I've tested the checksums and they all looks correct, could you please clear and re-download your sources with git clean -f; makepkg --verifysource.

I have the same issue as @jemappelle

This is no longer "community/paraview installed to /opt" since the change of dependencies from the 5.8.1 commit were not applied to this package.

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

I am not an expert and actually I have no idea what I am talking about means but with some research the solution was (at least in my case) to change in the PKGBUILD file in the sha256sum section the second list of numbers with this one: 9760a7ba33c6f46e3cb8dc8d0e2370ee1208d759b3c8c6c304e7e4b366391a13

Anyway, maybe the maintainer could change it and if not I hope it can help you.

Some good news for a change? Here it comes:

The current PKGBUILD is perfect w.r.t. to enabling -DH5_USE_110_API. No change required. Why do I tell you that?

I just got notified that the paraview maintainer has fixed FS#66441 - [paraview] Fix CFLAGS, CXXFLAGS. So I looked how he did it, and it boiled down to a simple

export CPPFLAGS+=" -DH5_USE_110_API"

But how can that work? CMake is known to ignore CPPFLAGS!

I rebuilt the paraview package and checked: Indeed, its build.ninja had the correct FLAGS.

The explanation is that Arch Linux has the cmake package patched (since version 3.17.3) so that it honors CPPFLAGS. Debian seems to have made that move long before. The AUR package cmake-git also includes the patch.

But we fixed the PKGBUILD for paraview-opt before, assuming unpatched CMake. Are those flags now duplicated?

(In the patches that I proposed, the required definition would be added to CPPFLAGS, which would then be added to CMake analogs of CFLAGS and CXXFLAGS, therefore a patched CMake would use them twice per compilation command.)

No duplication! Because this PKGBUILD does not duplicate CPPFLAGS at all:

FLAGS="-DH5_USE_110_API"
CFLAGS+=" ${FLAGS}"
CXXFLAGS+=" ${FLAGS}"
export CFLAGS CXXFLAGS

It adds the required flag to CFLAGS, CXXFLAGS directly.

In other words, this PKGBUILD works with both unpatched and patched CMake.

But there is a difference, right? Yes: With the patched CMake, distributed since 3.17.3, the build flags now also include CPPFLAGS (which usually has -D_FORTIFY_SOURCE=2 as per /etc/makepkg.conf). We get this improvement for free, no action required. Have a nice day.

Hi, I did an update yesterday and have following error with paraview-opt: paraview: symbol lookup error: /usr/lib/libospray_common.so.0: undefined symbol: _ZN3tbb10interface78internal15task_arena_base24internal_max_concurrencyEPKNS0_10task_arenaE

after traduction with c++filt: paraview: symbol lookup error: /usr/lib/libospray_common.so.0: undefined symbol: tbb::interface7::internal::task_arena_base::internal_max_concurrency(tbb::interface7::task_arena const*)

Am I the only one? Is it specific to my machine? Paraview-opt was working last week.

Thanks for your feedback,

@bartus Thanks! I've changed the makeflags entry in makepkg.conf from j3 to j1 and the problem has solved.