> From: David Knezevic <dk...@mi...> -  2009-03-24 18:29
> Just to follow up on Paulo's message, I'm now running the libmesh SVN
> head with petsc-3.0.0-p4 and slepc-3.0.0-p2, and it works nicely. This
> fixes the error with slepc 2.3.3 that Paulo mentioned. By the way, I
> encountered the same error with slepc 2.3.3, but I just commented out:
>
> ierr = EPSDestroy(_eps);
> CHKERRABORT(libMesh::COMM_WORLD,ierr);
>
> in SlepcEigenSolver::clear, which fixed the problem. This at least
> allows you to see the perf_logging output etc at the end of the  
> program
> (I'm with Derek, this doesn't count as a memory leak :).
>
> I did run across one issue in configuring libmesh with slepc-3.0.0
> though. For me, after configuring, SLEPC_INCLUDE was set to:
>
> "-I/home/dave/slepc-3.0.0-p2
> -I/home/dave/slepc-3.0.0-p2/linux-gnu-c-debug/include
> -I/home/dave/slepc-3.0.0-p2/include"
>
> where "linux-gnu-c-debug" is my PETSC_ARCH. I had to remove the first
> two of these include lines to get it to compile properly.
>
> - Dave


You are right, we made a change in trunk/libmesh/Make.common.in:396  
that probably should be reverted (though it was not a problem for us):

libmesh_INCLUDE += "\${SLEPC_INCLUDE}"

should be changed to

libmesh_INCLUDE += -I$(SLEPC_DIR)/include

Can someone change this in the repository?
Thanks,
Jose


------------------------------------------------------------------------------
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to