When using petsc-2.3.3+tao-1.9, TAO does require that PETSc be built with C++. I believe this is just because a PETSc built with C cannot always provide enough info to TAO makefiles about the C++ compiler... However, when PETSc is built with a external that requires C++/mpicxx, then it seems some C++ stuff is configured even when core PETSc is compiled with C/mpicc.
IMHO, this is a bit annoying, and could be done better and probably with no too much work... Could PETSc BuildSystem try to configure both C and C++ despite the actual value of --with-clanguage ?? Does this make sense? -- Lisandro Dalc?n --------------- Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC) Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC) Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET) PTLC - G?emes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594
