From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24765 invoked by alias); 19 Mar 2011 09:49:48 -0000 Received: (qmail 24742 invoked by uid 22791); 19 Mar 2011 09:49:46 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 19 Mar 2011 09:49:42 +0000 From: "mikestump at comcast dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/44107] libstdc++ (dylib) is built with an erroneous dependency towards /usr/lib X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mikestump at comcast dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sat, 19 Mar 2011 11:42:00 -0000 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: 2011-03/txt/msg02088.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44107 --- Comment #3 from Mike Stump 2011-03-19 09:49:35 UTC --- > With an appropriate DYLD_LIBRARY_PATH, the problem disappears. So, can you elaborate? Which value makes the problem disappear? I'd assume you if you include $prefix/lib? I fear this is going to be a hard bug... If one wants any compatibility, the routines in gcc_s from /usr/lib have to be used, in particular, the unwinder. But, that is exactly the thing that appears to be causing the problems. I think we're going to need a test case, or if you could, could you try and binary search the gcc trunk for the patch that caused this to break for you? Also, you have this in bootstrap, does that mean that this doesn't bootstrap? If you could include the error messages from the bootstrap, or the name of the gcc test case in the testsuite that is failing, that would help. Thanks.