[MacPorts] #43828: clang-3.4 package uses mismatched libc++ headers and libraries

[Jeremy Huddleston Sequoia]

On May 26, 2014, at 11:14, Jack Howarth <howarth.at.macports at gmail.com> wrote:

> While I think the inverse would be safe, i.e. using the older system libc++ headers with the newer libc++ shared libraries (as long as there hasn't been an so version bump), I don't see how the mixing of newer headers with older shared libraries can possibly be safe as the newer header may well define new calls, etc not present in the older shared library.

Yes, and if that's the case (which isn't actually quite frequent), the user will get an error at link time that will be obvious.  As solution, they can either install a newer C++ runtime than is provided by their host OS or upgrade to a newer host OS with a newer C++ runtime.

With your fink case, users will get successful linking, and things will fall apart at runtime as different libraries try to share objects across C++ runtimes.

--Jeremy