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.000000
First Submitted: 2017-09-25 09:46 (UTC)
Last Updated: 2020-06-22 10:15 (UTC)

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

« First ‹ Previous 1 2 3

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.

« First ‹ Previous 1 2 3