[petsc-dev] [petsc-maint] problem installing petsc 3.4

[Jed Brown]

Sean Farley <sean.michael.farley at gmail.com> writes:
>> 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 :-)

Yup, and this brings in the next bag of worms.  My understanding is that
clang needs -stdlib=libc++ or -stdlib=libstdc++ at compile-time to match
that passed at link-time (perhaps manually to the linker).  Is there any
way to determine what the default is?

It's nice how they soaked up the stdlib namespace to be C++-specific
because everyone knows that libc will always be binary-compatible and
that other languages will never be standard.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140416/fa4ae234/attachment.sig>