From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1446 invoked by alias); 10 Nov 2005 03:04:33 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 1402 invoked by alias); 10 Nov 2005 03:04:27 -0000 Date: Thu, 10 Nov 2005 03:04:00 -0000 Message-ID: <20051110030427.1391.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/24718] Shared libgcc not used for linking by default In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "wilson at tuliptree dot org" X-SW-Source: 2005-11/txt/msg01394.txt.bz2 List-Id: ------- Comment #9 from wilson at tuliptree dot org 2005-11-10 03:04 ------- Subject: Re: Shared libgcc not used for linking by default On Wed, 2005-11-09 at 16:08, sje at cup dot hp dot com wrote: > I tried Jim Wilson's suggested changes (with 3.4.4 GCC) but they didn't > seem to fix the problem. Try debugging init_specs where it calls init_gcc_specs. There might be something about the code that is causing it to misbehave for you. Don't configure with --disable-shared, that will prevent this code from doing anything. It occurred to me that another possible solution is to change init_specs and/or the ia64-hpux LIBGCC_SPEC so that all uses of -lgcc will be replaced instead of just the first one. That would also fix the problem. Looking at the code, I think adding a space before the second -lgcc in the current ia64-hpux LIBGCC_SPEC would do the trick, because that will cause in_sep to be set again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24718