Date: Wed, 3 Jan 2001 15:24:29 -0600 From: "Jim King" <jim@jimking.net> To: "Daniel Eischen" <eischen@vigrid.com> Cc: <stable@FreeBSD.ORG> Subject: Re: Threaded C++ Question Message-ID: <015801c075cb$91f86580$524c8486@jking> References: <Pine.SUN.3.91.1010103161116.10340A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Daniel Eischen" <eischen@vigrid.com> wrote: > On Wed, 3 Jan 2001, Jim King wrote: > > "Daniel Eischen" <eischen@vigrid.com> 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.... The binary was built back in October. This is the same binary that failed on 4.2-RELEASE and -stable's as of a couple weeks ago. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?015801c075cb$91f86580$524c8486>