From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15230 invoked by alias); 20 Mar 2011 20:34:58 -0000 Received: (qmail 15131 invoked by uid 22791); 20 Mar 2011 20:34:58 -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; Sun, 20 Mar 2011 20:34:54 +0000 From: "Denis.Excoffier at airbus dot com" 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: Denis.Excoffier at airbus dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.1 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: Sun, 20 Mar 2011 21:10: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/msg02163.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44107 --- Comment #10 from Denis Excoffier 2011-03-20 20:34:37 UTC --- (In reply to comment #8) > "DYLD_PRINT_LIBRARIES=1 ./myexe " > is really useful for making sure that the libraries you think should be used > actually are ;-) This is great, thank you for the hint. This shows that the sets 'y' (ie patched) and 'z' (ie unchanged) have a real dependency towards /usr/lib/libgcc_s.1.dylib. The set 'x' (modif t-slibgcc-darwin) does not have it. Perhaps (i don't know) it is inside anyway (i mean statically) but i suppose that if some libgcc_s.1.dylib must be statically included, the one just-compiled will be chosen. Now comes the question of the beginning (which is also included in the title of this PR): why does my C++ program have (like in 'y' or 'z'+DYLD_LIBRARY_PATH) to use a /usr/lib/libgcc_s.1.dylib (dated 2007-10-06, 264016 bytes on my Darwin 9.8.0), when we could take advantage of the one in $(prefix)/lib (newer and only 89656 bytes), or none at all (like in 'x')? Second question, why is /usr/lib hardwired into t-slibgcc-darwin (line 31)? That fact, let it alone, is already suspicious for me...