From owner-freebsd-current Tue May 26 08:31:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16416 for freebsd-current-outgoing; Tue, 26 May 1998 08:31:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16401 for ; Tue, 26 May 1998 08:31:52 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA22406; Tue, 26 May 1998 09:31:11 -0600 (MDT) Message-Id: <199805261531.JAA22406@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: John Polstra cc: John Birrell , tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Mon, 25 May 1998 20:52:18 PDT." <199805260352.UAA18333@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 09:31:11 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > BTW, what's you opinion of egcs? > > It seems to have frequent ups and downs. We have been using the > Feb. 21 snapshot for a fairly large C++ project that I'm involved > with, and we haven't had any show-stopper problems. But I believe > some of the other team members tried a later snapshot and ran into all > sorts of bugs. > > One thing I can say is that the template support is immeasurably > better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but > I've heard that its C++ support is much improved over 2.7.2 as well. We're doing a complex c++/pthreads project and found that neither 2.7.2 or 2.8.1 worked for us, but an egcs snap from several months ago works well. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message