Package Base Details: openfoam

Git Clone URL: https://aur.archlinux.org/openfoam.git (read-only, click to copy)
Submitter: None
Maintainer: petronny (AutoUpdateBot)
Last Packager: AutoUpdateBot
Votes: 60
Popularity: 0.82
First Submitted: 2009-07-02 09:16 (UTC)
Last Updated: 2024-04-01 17:32 (UTC)

Packages (1)

Pinned Comments

petronny commented on 2020-08-04 08:36 (UTC) (edited on 2023-04-14 08:48 (UTC) by petronny)

Pre-built binaries of this package and its dependencies can be found in the arch4edu repository.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 27 Next › Last »

D0NB0T commented on 2016-06-17 19:08 (UTC) (edited on 2016-06-17 20:16 (UTC) by D0NB0T)

I tried this already and reimported all keys. Same Error with the Minerva Package. But the AUR Paraview and Scotch Packages seem to work now. Edit: Ok now it works with paraview and scotch from AUR and OpenFoam from Minerva, because OpenFoam from AUR couldnt be installed, it always stopped while building. I hope this will do it.

Xwang commented on 2016-06-17 18:09 (UTC)

https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28invalid_or_corrupted_package.29.22_error

D0NB0T commented on 2016-06-17 17:32 (UTC)

I always get the Error: "Failed to commit transaction (invalid or corrupted package)" while downloading. I tried installing from AUR and Minerva always the same error for Paraview and Scotch. It worked fine before the last update. Any suggestions? Thanks for your help!

Xwang commented on 2016-06-13 16:17 (UTC) (edited on 2016-06-13 16:17 (UTC) by Xwang)

Change the MAKEFLAGS option in /etc/makepkg.conf (I've set it to MAKEFLAGS="-j5" to use 5 cores of 8 so that the system responds while compiling and I can keep using it). See https://wiki.archlinux.org/index.php/Makepkg#Improving_compile_times

ioquatix commented on 2016-06-12 23:14 (UTC)

Interesting, can you show me the config you have for pacman?

Xwang commented on 2016-06-12 16:12 (UTC)

I can confirm you that it uses all the core I've set in the pacman configuration file. The log file remains in the directory where the PKGBUILD is (without logging it will be impossible to read warnings and errors at compilation time).

ioquatix commented on 2016-06-12 14:57 (UTC)

Also, why do you eat the build log.. i prefer to see output/progress/errors # Build and clean up OpenFOAM ./Allwmake > ../../openfoam_log.make 2>&1 #|| return 1 right now, openfoam builds but due to some issues in https://aur.archlinux.org/packages/scotch/ I just submitted a fix so that it links correctly, but openfoam build fails to build decomposePar, etc due to this issue, but the problem is silently ignored by the build system here for some reason?

ioquatix commented on 2016-06-12 14:54 (UTC)

@xwang I don't believe it is, as this is using wmake which doesn't have anything to do with pacman?

Xwang commented on 2016-06-12 14:13 (UTC)

@ioquatix I do not know if it is the same, but I have configured my pacman to use the maximum number of cores I want (one less than the output of nproc in my case) and it uses them to build.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 27 Next › Last »