From owner-freebsd-current Mon Nov 16 08:37:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28795 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:37:54 -0800 (PST) (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 IAA28782 for ; Mon, 16 Nov 1998 08:37:52 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id JAA22267; Mon, 16 Nov 1998 09:45:39 -0700 (MST) Message-Id: <199811161645.JAA22267@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: newer gcc? In-reply-to: Your message of "Mon, 16 Nov 1998 07:06:33 +0100." <19981116070633.A13428@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Nov 1998 09:45:38 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > According to Terry Lambert: > > unless you compile it with threading enabled (unlike g++ 2.8.1, you > > must choose threading or no threading for resulting binaries at the > > time you compile the compiler, not at the time you compile the > > program). > > Last time I looked at a generic gcc 2.8.1, it also required you to specify > --enable-threads for configure. Are you really sure about this big > difference between egcs & gcc ? A quick scan of the 2.8.1 source leads me to believe that this is only for objective-c thread support. We are successfully using gcc 2.8.1 with threads in a fairly complex project, didn't need to use 'enable-threads'. However we did need to patch both gcc and libc_r source to handle exceptions (see the archives for my patches). -- 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