From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 640 invoked by alias); 29 Feb 2008 16:53:01 -0000 Received: (qmail 461 invoked by uid 48); 29 Feb 2008 16:52:12 -0000 Date: Fri, 29 Feb 2008 16:53:00 -0000 Message-ID: <20080229165212.460.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/35401] libstdc++ linked to system /usr/lib/libgcc_s.1.dylib not new gcc4.3 libgcc_s.1.dylib In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "howarth at nitro dot med dot uc dot edu" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-02/txt/msg02990.txt.bz2 ------- Comment #10 from howarth at nitro dot med dot uc dot edu 2008-02-29 16:52 ------- Regressing r131198 eliminates the problem here... 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) ...at least for a manual rebuilding of the gcc and other library build directories. I'll do a complete build of gcc trunk with r131198 regressed next. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35401