Package Details: openfoam-org 12.20250206-4

Git Clone URL: https://aur.archlinux.org/openfoam.git (read-only, click to copy)
Package Base: openfoam
Description: The open source CFD toolbox (www.openfoam.org)
Upstream URL: http://www.openfoam.org
Licenses: GPL-3.0-or-later
Provides: openfoam
Submitter: None
Maintainer: envolution
Last Packager: envolution
Votes: 64
Popularity: 0.167188
First Submitted: 2009-07-02 09:16 (UTC)
Last Updated: 2025-02-07 05:05 (UTC)

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 Next › Last »

kragacles commented on 2011-06-23 18:13 (UTC)

Glad to help! Let me know if you find any other trouble with the package. OpenFOAM can be quite the beast to maintain.

<deleted-account> commented on 2011-06-23 17:54 (UTC)

Thank you very much for your help. Also kudos on your rapid response. It has now installed successfully.

kragacles commented on 2011-06-22 20:46 (UTC)

Your openmpi environment is improperly setup, possibly from an old OpenFOAM install that pointed to the old 1.7.3 ThirdParty library version of openmpi. For a system install of openmpi 1.5.3-3 "mpicc -showme" should return "gcc -pthread -L/usr/lib/openmpi -lmpi -ldl". That is why ptscotch is failing to build. You will want to clean out any old OpenFOAM and ThirdParty versions which could have installed an openmpi environment; pay special attention to anything in /etc/profile.d/ or /etc/ld.so.conf.d/ that involves openfoam or openmpi. Then logout/in or just restart to clear your environment variables like PATH. Both OpenFOAM and openmpi really fill up your environment. If the problem persists you might need to go to the arch forums or openmpi (http://www.open-mpi.org/) to find out what might be overwriting the environment for your system install of openmpi (1.5.3-3). I'm afraid I am not an expert.

<deleted-account> commented on 2011-06-22 20:06 (UTC)

mpicc -showme returns "Cannot open configuration file /opt/OpenFOAM/ThirdParty-1.7.1/platforms/linux64Gcc/openmpi-1.4.1/share/openmpi/mpicc-wrapper-data.txt Error parsing data file mpicc: Not found" pacman -Qi openmpi says I have version 1.5.3-3 installed It fails on bdgraph_bipart_df.o when installing the dependency ptscotch-openmpi

kragacles commented on 2011-06-22 19:16 (UTC)

It seems like OpenFOAM is trying to use their own Thirdparty OpenMPI instead of the system OpenMPI, which should be installed as a dependency of paraview. The file prefs.sh which gets added by the PKGBUILD sets WM_MPI=SYSTEMOPENMPI, which uses mpicc -showme to properly fill out the openmpi paths. Can you verify that the command "mpicc -showme" works, do a "pacman -Qi openmpi" for details which one is installed, and can you share which file(s) the compile fails on for you?

<deleted-account> commented on 2011-06-22 18:59 (UTC)

This isn't compiling for me (v.2.0.0) it's looking for files in a third party folder (Cannot open configuration file /opt/OpenFOAM/ThirdParty-1.7.1/platforms/linux64Gcc/openmpi-1.4.1/share/openmpi/mpicc-wrapper-data.txt) that don't exist.

kragacles commented on 2011-06-20 14:19 (UTC)

OpenFOAM 2.0.0 is up. Biggest changes are here: http://www.openfoam.com/version2.0.0/ The dependencies have changed to include parmetis (which includes metis), scotch and ptscotch-openmpi. Paraview is no longer optional. The system install of openMPI is used by default.

kragacles commented on 2011-06-17 15:40 (UTC)

Openfoam 2.0.0 was released yesterday! I'm running through the builds right now, and will have updated packages up later today. I also believe I have figured out the openmpi issues, and the problems with Metis and Scotch decomposition methods. Just requires some minor patching for some arch specific dependencies.

kragacles commented on 2011-03-07 15:03 (UTC)

I have an idea as to why openmpi isn't working properly with OpenFOAM. The OpenFOAM path setup appears to cause openmpi to look for some settings in the ThirdParty libraries, even if you have not installed the full ThirdParty group and are instead using a system openmpi. I actually ran across this when building another package with openmpi, and I traced the cause to OpenFOAM. I am going to step back through the OpenFOAM configs and find out where this is happening. It shouldn't be too hard to force OpenFOAM to use the system openMPI.