Package Details: elmerfem 9.0-4

Git Clone URL: https://aur.archlinux.org/elmerfem.git (read-only, click to copy)
Package Base: elmerfem
Description: A finite element software for multiphysical problems
Upstream URL: http://www.elmerfem.org
Keywords: CFD FEM simulation
Licenses: GPL
Conflicts: elmerfem-git
Submitter: saxonbeta
Maintainer: rmsc
Last Packager: rmsc
Votes: 12
Popularity: 0.044457
First Submitted: 2015-08-18 13:50 (UTC)
Last Updated: 2023-11-22 20:14 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

ttshaw1 commented on 2022-02-26 06:36 (UTC)

Looks like I'm the first one to have problems relating to Python. After manually installing ospray and openvr, I'm not a point where I get the following error message: -- Could NOT find Qt3 (missing: QT_QT_LIBRARY QT_INCLUDE_DIR)

CMake was unable to find desired Qt version: 3. Set advanced values QT_QMAKE_EXECUTABLE and QT3_QGLOBAL_H_FILE.

-- [ElmerGUI] Qwt: TRUE

-- [ElmerGUI] QWT_LIBRARY: /usr/lib/libqwt.so

-- [ElmerGUI] QWT_INCLUDE_DIR: /usr/include/qwt


-- Found Embree v3.13.3: /usr/lib/libembree3.so.3.13.3

-- Found Open VKL v1.1.0: /usr/lib/libopenvkl.so.1.1.0

-- Found OSPRay: /usr

-- Found OpenVR: /usr/lib/libopenvr_api.so

-- Could not find the VTK package due to a missing dependency: OpenVR

-- Found FontConfig: /usr/lib/libfontconfig.so

-- Could not find the VTK package due to a missing dependency: FontConfig

CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find Python (missing: Python_EXECUTABLE Interpreter)

Call Stack (most recent call first):

/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)

/usr/share/cmake/Modules/FindPython.cmake:561 (find_package_handle_standard_args)

/usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)

/usr/lib64/cmake/vtk/Findmpi4py.cmake:2 (find_dependency)

/usr/lib64/cmake/vtk/VTK-vtk-module-find-packages.cmake:415 (find_package)

/usr/lib64/cmake/vtk/vtk-config.cmake:150 (include)

ElmerGUI/CMakeLists.txt:93 (FIND_PACKAGE)

Anyone know how to handle this?

Kitpaddel commented on 2021-08-21 10:09 (UTC)

Was able to compile by adding this line to the prepare() section of the PKGBUILD

sed -i 's/sprintf(str_pstr, fmt);/sprintf(str_pstr, "%s", fmt);/g' matc/src/str.c

gpettinello commented on 2021-08-08 17:40 (UTC)

@phollox: same error. It is strange as matc and in particular str.c is present also in other parts of elmer. And they don't give error

phollox commented on 2021-05-12 14:05 (UTC) (edited on 2021-05-12 14:12 (UTC) by phollox)

Trying to build it. Got this far:

[  3%] Building C object matc/src/CMakeFiles/matc.dir/str.c.o
/home/phollox/.cache/yay/elmerfem/src/elmerfem-release-9.0/matc/src/str.c: In function ‘str_sprintf’:
/home/phollox/.cache/yay/elmerfem/src/elmerfem-release-9.0/matc/src/str.c:85:5: error: format not a string literal and no format arguments [-Werror=format-security]
   85 |     sprintf(str_pstr, fmt);
      |     ^~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [matc/src/CMakeFiles/matc.dir/build.make:328: matc/src/CMakeFiles/matc.dir/str.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:14490: matc/src/CMakeFiles/matc.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error making: elmerfem

Hey, at least is not gfortran complaining....

DarioP commented on 2020-11-06 13:06 (UTC)

In case anyone is wondering if the package builds without intervention, as of today the answer is still no.

a.kudelin commented on 2020-06-07 16:35 (UTC)

@hacksd, you're right, the package cannot be built due to a bug in gcc-fortran. It has already been fixed in the development branch of GCC, and I filed a request to maintainers to apply corresponding patch in archlinux. Suggest to wait a bit, or as a temporary solution you may use a different compiler until packages being fixed.

hacksd commented on 2020-06-04 21:54 (UTC)

But even after that, I faced multiple issues some of which are reported in the GitHub repo. Finally building from source is what worked for me.

The release used by this package, though being latest, can't be built with gfortran 10 so should this package be flagged as out-of-date?

hacksd commented on 2020-06-04 21:50 (UTC)

I tackled that issue with the help of the contributors in this issue. I basically added this sed command in the PKGBUILD before the cmake command:

sed -i -e 's/{CMAKE_Fortran_FLAGS}/{CMAKE_Fortran_FLAGS} -fallow-argument-mismatch/g' ../$pkgname-release-$pkgver/CMakeLists.txt

hacksd commented on 2020-06-03 06:28 (UTC)

Hello, thanks for this package. I am facing this error when trying to build this package:

    [  3%] Building Fortran object mathlibs/src/arpack/CMakeFiles/arpack.dir/cnaitr.f.o
/home/sudhanshu/builds/elmerfem/src/elmerfem-release-8.4/mathlibs/src/arpack/cnaitr.f:666:35:

  383 |             call svout (logfil, 1, rnorm, ndigit,
      |                                   2
......
  666 |             call svout (logfil, 2, rtemp, ndigit,
      |                                   1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1)

Any help is welcome.

a.kudelin commented on 2020-04-28 09:50 (UTC)

@CrocoDuck, hi!
I've added a commented check() section to a PKGBUILD, unfortunately, only 96% of tests are passed at the moment, hopefully I will tackle the rest in the next release. None of tests are failing with SIGSEGV, so I'd recommend you (a) to review compiler flags you're passing while building. It could be done in /etc/makepkg.conf, and (b) to look at dependencies of elmer, maybe some of them are out of date on your PC and this produces errors. Also compiling the package with -g option followed by examination of run with valgrind could help to locate the source of the issue.