On Fri, 29 Feb 2008, Yujie wrote: > Now, I want to use TAO package in my libmesh code, which is developed based > on PETSc. I must configure PETSc with "--with-clanguage=C++" according to > TAO installation guide. any solution to it? thanks a lot.
Hmmm... I'm not sure, but I'll copy this back to the list in case anyone else has ideas; it sounds like you've got a real problem. I don't have time to look at this right now, but it may be possible for our configure scripts to autodetect how PETSc was compiled and to remove the obstacles to linking against a C++ PETSc if necessary. What is causing the linking errors, the "extern "C"" directives we wrap around the PETSc headers for C compatibility? It looks like we already turn that off when using --enable-complex; we ought to be able to turn it off in other cases as well. If that's the only problem, Yujie, as a temporary workaround you might try commenting out those directives by hand, and see if that fixes it. --- Roy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
