Jed Brown <[email protected]> writes: > Satish Balay <[email protected]> writes: > >> On Wed, 16 Apr 2014, Jed Brown wrote: >> >>> Yes, but the current failure case is complicated because people see a >>> library they've never heard of and probably is not documented anywhere. >>> "How did PETSc come up with this insane thing?" I wouldn't take CMake >>> as a model actor (it's inherent assumptions seem to break more than we >>> do), but they use the Fortran compiler to link and don't try to include >>> private libraries on the link line. >> >> Perhaps things have improved now. There used to be a bunch of c++ >> compilers which requilred cxx as the linker for a c++ main. > > When PETSc is built as a C library depending on some C++ package (e.g., > Elemental), we should have a reliable way for users to link independent > of whether their main is C, C++, or Fortran. My recollection is that in > the majority of cases, C++ ends up just needing -lstdc++ while Fortran > has all manner of idiosyncrasies.
You misspelled '-lc++' for Mavericks :-)
