On Fri, Aug 16, 2013 at 8:51 AM, Jens Lohne Eftang <[email protected]>wrote:
> Yes, so this is embarrassing: > > Prior to my first post I configured libmesh _and_ petsc for complex but > did not use --with-clanguage=cxx. When recompiling I forgot > --enable-complex for libmesh, so you are right. > > So the conclusion was that --with-clanguage=cxx for petsc did the trick. > > Why do I need this for complex support exactly? > I think --with-clanguage=cxx causes the complex type in PETSc to be std::complex<double>, while without it, the complex type is something else C-based (not sure exactly what that's called). The former seems to work OK with libmesh but not the latter. -- John ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
