Richard,
This problem appears to be caused by...
Author: rsandifo
Date: Thu Dec 27 11:26:06 2007
New Revision: 131198
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131198
Log:
libgcc/
* Makefile.in (all): Use install-leaf rather than install.
(install): Split most of the rule into...
(install-leaf): ...this new one.
Modified:
trunk/libgcc/ChangeLog
trunk/libgcc/Makefile.in
...regressing that patch for my existing build and rebuilding the
gcc shared libraries eliminates the problem...
otool -L libgfortran.3.dylib
libgfortran.3.dylib:
/sw/lib/gcc4.3/lib/libgfortran.3.dylib (compatibility version 4.0.0,
current version 4.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.0.0)
/sw/lib/gcc4.3/lib/libgcc_s.1.dylib (compatibility version 1.0.0,
current version 1.0.0)
I am repeating a complete bootstrap with that patch regressed as
an additional confirmation.
Jack
On Fri, Feb 29, 2008 at 05:04:53PM +0100, Richard Guenther wrote:
> On Fri, Feb 29, 2008 at 3:14 PM, Jack Howarth <[EMAIL PROTECTED]> wrote:
> > Current gcc 4.3 branch incorrectly links all of its
> > shared libraries against the system libgcc instead of
> > the copy it builds and installs (PR35401). It appears
> > that the fix applied for PR30572 may have been
> > disturbed since it is no longer working.
> > Shouldn't PR35401 be escalated to a release blocker
> > for gcc 4.3.0?
>
> As this only seems to affect darwin, no.
>
> Richard.
