Package Details: openfoam-com v2012-1

Git Clone URL: (read-only, click to copy)
Package Base: openfoam-com
Description: The open source CFD toolbox (
Upstream URL:
Licenses: GPL
Submitter: dl6tud
Maintainer: dl6tud
Last Packager: dl6tud
Votes: 7
Popularity: 0.055408
First Submitted: 2020-12-24 16:36
Last Updated: 2020-12-24 16:36

Latest Comments

MakisH commented on 2020-10-05 21:03

@dl6tud there is now an openfoam-selector package and you can add a .install to register/deregister the OpenFOAM installation, as described in this issue.

MakisH commented on 2020-10-03 10:43

Pre-built binaries are now available in arch4edu. See instructions in the wiki.

MakisH commented on 2020-08-06 16:19

@dl6tud the package now built like a charm and everything (that I checked/need) seems to work well. Thank you very much for all the effort!

dl6tud commented on 2020-08-06 09:32

I removed the ThirdyParty now completely, and replaced paraFoam by "paraFoam -builtin". I had problems compiling scotch; "ptscotch" still does not work.

I removed "press key", and added "exit 1".

MakisH commented on 2020-08-06 07:28

I managed to build this now (hint: make sure you have enough memory, or reduce your number of building threads), but I think there is a mixing of dependencies between system (/usr/lib) and bundled (ThirdParty-v2006). In particular, fftw.

When I try to build an OpenFOAM function object (a shared library that links to OpenFOAM, specifically, I get runtime linking errors (check with ldd <library> or here read the ldd.log):

... => /usr/lib/ (0x00007ff47417f000) => /opt/OpenFOAM/ThirdParty-v2006/platforms/linux64Gcc/fftw-3.3.7/lib64/ (0x00007ff47405e000)
undefined symbol: fftw_taint    (/usr/lib/
undefined symbol: fftw_join_taint       (/usr/lib/

Do we really need to build the ThirdParty-v2006 dependencies? Isn't everything already described as a package dependency?

MakisH commented on 2020-08-02 08:13

Thank you for actively maintaining this package. I have two issues/suggestions trying this package on Manjaro 20.0.3, but should also affect Arch:

  • Issue 1. The prepare() and build() ask for user input ("press any key to continue"). This makes automation difficult, does not work with some GUI package managers such as Manjaro's Pamac, and may surprise the user that knows that building will take quite some time so goes through the usual process in the beginning and leaves the building unattended.

I understand the intention to make sure the user understands the problem before continuing, but I would suggest adding an explicit "Warning:" (maybe with some color characters) and removing the "press any key", or even aborting and advising to edit the PKGBUILD or take some other action.

  • Issue 2. This built "successfully" (falsely) unusually fast on my system (1-2h instead of expected 3-5h), only to realize later that the solvers were not built because of an error:
make: *** [/var/tmp/pamac-build-tester/openfoam-esi/src/OpenFOAM-v2006/wmake/rules/General/transform:35: /var/tmp/pamac-build-tester/openfoam-esi/src/OpenFOAM-v2006/build/linux64GccDPInt32Opt/src/thermophysicalModels/chemistryModel/chemistryModel/TDACChemistryModel/reduction/makeChemistryReductionMethods.o] Error 1

One problem here is the actual error, but this is probably upstream (I opened an issue there) -- UPDATE: It was only that my system ran out of memory.

An issue concerning the package is that, despite this error, PKGBUILD continues to package(), which then leads to a half-baked installation.

Interestingly, the same error appears in the openfoam package (OpenFOAM 7), but there this error is caught like this:

  # Build and clean up OpenFOAM
  bash -c "source ${foamDotFile}
  ./Allwmake || exit 1
  wclean all || exit 1
  wmakeLnIncludeAll || exit 1"