[dune-fem] Error linking UMFPACK
Andreas Dedner
a.s.dedner at warwick.ac.uk
Tue Jun 10 19:29:43 CEST 2014
I think most dune-fem user just go with the
ALL_PKG_*
flags as for example also done in the howto.
I hope that works, best
Andreas
@Claus: I don't quite see what the difference between your
ALL_DUNE_FEM_FLAGS and ALL_PKG_FLAGS would be. Basically if my modules
depends on
dune-fem and lets say some dune-foo then I could have flags
ALL_DUNE_FEM_FLAGS and ALL_DUNE_FOO_FLAGS which I would have to add but
together
they would be identical to the ALL_PKG_FLAGS. Or am I missing something
in your suggestion?
Basically I guess the dune idea is to have the option
to really pick and choose - so my dune-fem was configured with petsc and
umfpack and I need that for some of my projects but some other module
I'm working on is an explicit fv needing neither so I don't add their
flags.
Alternatively if I'm lazy I use ALL_PKG...
On 10/06/14 17:32, Agnese, Marco wrote:
> Hello DUNEers,
> I have a problem with UMFPACK.
> I created a project (DUNE 2.3.0 and DUNE FEM 1.4) linking UMFPACK and it is correctly recognized:
> ------------------------------------------------------------------------------
> - SUMMARY -
> ------------------------------------------------------------------------------
>
> dune-common.............: version 2.3.0 (/usr/local_machine/dune-2.3.0/dune-common-2.3.0)
> dune-dynamic-grid.......: version 1.0 (/home/ma/m/ma2413/dune-repo/dune-dynamic-grid)
> dune-fem................: version 1.4.0 (/usr/local_machine/dune-2.3.0/dune-fem-1.4.0)
> dune-geometry...........: version 2.3.0 (/usr/local_machine/dune-2.3.0/dune-geometry-2.3.0)
> dune-grid...............: version 2.3.0 (/usr/local_machine/dune-2.3.0/dune-grid-2.3.0)
> dune-istl...............: version 2.3.0 (/usr/local_machine/dune-2.3.0/dune-istl-2.3.0)
> dune-localfunctions.....: version 2.3.0 (/usr/local_machine/dune-2.3.0/dune-localfunctions-2.3.0)
> dune-spgrid.............: version 2014.04 (/usr/local_machine/dune-2.3.0/dune-spgrid-2014.04)
>
> ALBERTA.................: version 3.0 (/usr/local_machine/alberta-3.0.0 ; world dims 1 2 3)
> ALUGrid.................: version 1.52 (parallel) (/usr/local_machine/alugrid-1.52)
> AmiraMesh...............: no
> BLAS....................: yes
> GMP.....................: yes
> Grape...................: no
> METIS...................: yes
> METIS...................: yes
> MPI.....................: yes (OpenMPI)
> OpenGL..................: yes (add GL_LIBS to LDADD manually, etc.)
> PETSc...................: no
> ParMETIS................: yes
> SIONLIB.................: no
> SuperLU-DIST............: no
> SuperLU.................: no
> UG......................: no
> UMFPACK.................: yes
> psurface................: no
>
> but when I compile my code HAVE_UMFPACK is 0 and ENABLE_UMFPACK is 0 and when I call the solveUMF it does nothing.
> If I set HAVE_UMFPACK = 1 and ENABLE_UMFPACK = 1 it doesn't compile because it doesn't find the UMFPACK header.
>
> I fixed it linking UMFPACK manually in the Makefile.am and it works but I would like to avoid it.
>
> What am I doing wrong?
>
> Thank you,
> cheers,
> Marco.
>
>
> _______________________________________________
> dune-fem mailing list
> dune-fem at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-fem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-fem/attachments/20140610/f007498d/attachment.htm>
More information about the dune-fem
mailing list