[Dune] problems with dune-functions building

Steffen Müthing steffen.muething at iwr.uni-heidelberg.de
Thu May 26 17:30:29 CEST 2016


Hi Francesco,

> Am 26.05.2016 um 17:22 schrieb Christoph Grüninger <christoph.grueninger at iws.uni-stuttgart.de>:
> 
> Hi Francesco,
> I don't know an answer to your problem, but I recognize the error.
> I did not yet find the time to pinpoint the problem. I switch to
> the compiler, from Clang or GCC or the other way round.
> I suspect a bad combination of Compiler and default includes.
> 
> Note that I am not using dune-functions but PDELab.

my guess is on a bug in either clang or libc++ (the C++ standard library shipped by Apple).

The easiest fix right now would be to switch to gcc (you can install that via homebrew). I’m running
on OS X 10.11.5 with GCC 6 and have no problems. There is one important thing, though: If you want
to switch to GCC, you have to recompile *all* C++ libraries in your stack (all dune modules and perhaps
also UG), otherwise you will get very weird linker errors or runtime crashes. That’s due to the two different
C++ standard libraries used by the two compilers.

Steffen

> 
> Bye
> Christoph
> 
> --
> On the one hand [computer "science"] has components
> of the purest of mathematics and on the other hand
> of the dirtiest of engineering. -- A. Oettinger 1967
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20160526/dabf6cf9/attachment.sig>


More information about the Dune mailing list