From owner-freebsd-stable Wed Jan 3 13:14:18 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 13:14:15 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 74B1537B400 for ; Wed, 3 Jan 2001 13:14:15 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA10799; Wed, 3 Jan 2001 16:13:51 -0500 (EST) Date: Wed, 3 Jan 2001 16:13:51 -0500 (EST) From: Daniel Eischen To: Jim King Cc: stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: <012701c075c4$13718360$524c8486@jking> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jan 2001, Jim King wrote: > "Daniel Eischen" wrote: > > > Mozilla M18 binary from mozilla.org runs fine. Cool! > > > > That's because they changed the mozilla port to work around the > > problem with libgcc (I believe with an explicit link -lgcc_r). > > This should be reverted once the correct fix is committed to > > libgcc and friends. > > But I didn't build Mozilla from the port, I downloaded the binary from > mozilla.org. Something in -stable must have changed since the last time I > tried to run the binary from mozilla.org. Well, here's the log from the port: revision 1.52 date: 2000/12/21 19:40:39; author: reg; state: Exp; lines: +2 -2 Explictly link against libgcc_r, to work around bugs in 4.2-RELEASE onwards and -CURRENT. I'm still not sure why the bug was exposed only recently, but it is due to libstdc++ being linked without the -nostdlib option (causing it to be statically linked against libgcc even for the threaded case). They could have used the same fix at mozilla.org.... -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message