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?
Jens
On 08/16/2013 10:37 AM, Roy Stogner wrote:
>
> The error here actually seems to suggest that PETSc is being compiled
> in complex mode:
>
>>> 'PetscScalar* {aka std::complex<double>*}'
>
> but libMesh is not:
>
>>> src/numerics/dense_matrix_blas_lapack.C:174:
>
> a line number wrapped in
> #if (LIBMESH_HAVE_PETSC && LIBMESH_USE_REAL_NUMBERS)
>
> ---
> Roy
------------------------------------------------------------------------------
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
