------- Comment #6 from echristo at apple dot com 2007-08-20 17:11 ------- No, I spoke to Daniel about it a while back, but he hasn't had time to look into it. It's definitely caused by the toplevel changes to libgcc. The basic idea is that the toplevel makefile re-installs libgcc into the gcc directory for some reason causing a relink of libgcc and since the is null the installed libgcc gets an install name of /libgcc_s.1.dylib. This is then used with libstdc++. When it's installed it is _again_ relinked and then has the proper install_name, but this won't fix the problem that libstdc++ has since it's already been linked in.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30572
