From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8959 invoked by alias); 20 Aug 2007 17:11:29 -0000 Received: (qmail 8206 invoked by uid 48); 20 Aug 2007 17:11:18 -0000 Date: Mon, 20 Aug 2007 17:11:00 -0000 Message-ID: <20070820171118.8204.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/30572] [4.3 Regression] target libraries links against /libgcc_s.1.dylib instead of $(prefix)/lib/libgcc_s.1.dylib In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "echristo at apple dot com" 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: 2007-08/txt/msg01414.txt.bz2 ------- 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