On Nov 17, 2013, at 14:02 , Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:
> Yes, there are. For instance the change in the default c++ runtime from
> libstdc++ to libc++ with OSX 10.9. These two runtimes cannot reliably be
> mixed, so rebuilding all ports is the only safe option. Yes, you might get by
> not doing this, for a while, but sooner or later you will run into problems,
> and the root cause is often hard to spot. users might consider the rebuild a
> pain, but the macPorts devs equally would consider the stream of 'bug'
> reports because this is not done, a pain... A rebuild is better all round, in
> the long term.
Given that macports::revupgrade_scanandrebuild is already scanning for broken
dylib dependencies, I think marking C++ runtime mismatches within the scanning
dependency graph would be well within its purview?
-landonf
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
