Package Details: freefem 4.5-1

Git Clone URL: https://aur.archlinux.org/freefem.git (read-only, click to copy)
Package Base: freefem
Description: A PDE oriented language using the finite element method
Upstream URL: https://freefem.org/index.html
Licenses: LGPL
Conflicts: freefem++
Provides: freefem++
Submitter: haawda
Maintainer: Sosthene
Last Packager: Sosthene
Votes: 15
Popularity: 0.89
First Submitted: 2019-06-19 19:31
Last Updated: 2020-02-13 22:01

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

holos commented on 2013-05-25 21:43

It was incorrect for me to have added umfpack as a conflict, according to https://bugs.archlinux.org/task/17625

Beyond adding a note, I don't know how to ignore the incompatible stuff from suitesparse. There doesn't seem to be anything relevant in the mailing list.

I'm also inclined to add --disable-pdf because the pdf is updated much more frequently than the tarball anyways.

holos commented on 2013-05-25 21:17

It was incorrect for me to have added umfpack as a conflict, according to https://bugs.archlinux.org/task/17625

Beyond adding a note, I don't know how to ignore the incompatible stuff from suitesparse. There doesn't seem to be anything relevant in the mailing list.

I'm also inclined to add --disable-pdf because the pdf is updated much more frequently than the tarball anyways.

viperpaulo commented on 2013-05-23 06:52

You can modify the PKGBUILD as follow :
- If you want to signal a conflict with umfpack :
conflicts=('umfpack')
provides=('umfpack')
This solves problems when you have another program which uses umfpack.
- You can also add this, which would be better I guess (not sure about that)
conflicts=('umfpack' 'suitesparse')
provides=('umfpack' 'suitesparse=4.0.2')
- I think that you can just not mention conflict with umfpack, it works well like that.

But I didn't find how to signal a conflict for compilation step, since it's impossible to compile when SuiteSparse is already installed and conflicts has effects on installation steps but not during compilation.

Also to solve multi-threads compilations problems you should add this to the PKGBUILD :
options=('!makeflags')
which will reset all makeflags during compilation.

viperpaulo commented on 2013-05-22 14:47

Hi,

Thx for this package !
I found why mrbit and others have some troubles :
- missing dep : metis
- export MAKEFLAGS="-j1"
- uninstall SuiteSparse to compile

hope this help !

Anonymous comment on 2013-05-07 17:18

I cannot compile MUMPS. It tells

Cannot open included file 'mpif.h'

Anonymous comment on 2013-05-07 17:16

holos commented on 2013-05-03 20:29

still builds here.

foobarrior commented on 2013-04-21 10:05

suddenly cannot build MUMPS=\

holos commented on 2013-01-09 02:37

umfpack is provided by suitesparse in extra. it should be fine as it is.

holos commented on 2013-01-09 02:34

umfpack is provided by suitesparse in extra. it should be fine as it is.