From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8412 invoked by alias); 14 May 2005 01:50:23 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 8389 invoked from network); 14 May 2005 01:50:17 -0000 Received: from unknown (HELO omta02sl.mx.bigpond.com) (144.140.93.154) by sourceware.org with SMTP; 14 May 2005 01:50:17 -0000 Received: from grove.modra.org ([144.136.167.90]) by omta02sl.mx.bigpond.com with ESMTP id <20050514015015.HWIK25875.omta02sl.mx.bigpond.com@grove.modra.org> for ; Sat, 14 May 2005 01:50:15 +0000 Received: by bubble.grove.modra.org (Postfix, from userid 500) id E95881A0A1E; Sat, 14 May 2005 11:20:15 +0930 (CST) Date: Sat, 14 May 2005 04:59:00 -0000 From: Alan Modra To: Paul Koning Cc: drow@false.org, binutils@sources.redhat.com Subject: Re: Unintellegible ld error messages Message-ID: <20050514015015.GC27573@bubble.grove.modra.org> Mail-Followup-To: Paul Koning , drow@false.org, binutils@sources.redhat.com References: <17026.22346.789514.57742@gargle.gargle.HOWL> <20050511191110.GA470@nevyn.them.org> <17029.942.76640.325068@gargle.gargle.HOWL> <20050513195035.GA19560@nevyn.them.org> <17029.2332.365233.194854@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17029.2332.365233.194854@gargle.gargle.HOWL> User-Agent: Mutt/1.4i X-SW-Source: 2005-05/txt/msg00468.txt.bz2 On Fri, May 13, 2005 at 04:07:56PM -0400, Paul Koning wrote: > It turns out that libgcc.so has _Unwind_GetIP as a regular symbol, but > libgcc.a has it as a hidden symbol. One of my builds only has the .a > version of libgcc, so that's why that link fails (while others for > another target work fine). _Unwind_GetIP as a hidden symbol in libgcc.a is not the problem. If you built libstdc++.so linked against libgcc_s.so, then when linking using libstdc++.so you need to have libgcc_s.so available, and, importantly, libgcc_s.so must be linked before libgcc.a if both are specified. If you built libstdc++.so only linked against libgcc.a, then you can use libstdc++.so like that too. -- Alan Modra IBM OzLabs - Linux Technology Centre