From owner-freebsd-alpha Wed Jan 9 12:20:37 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 866CD37B416 for ; Wed, 9 Jan 2002 12:20:11 -0800 (PST) Received: (qmail 20572 invoked from network); 9 Jan 2002 20:20:10 -0000 Received: from unknown (HELO server.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 9 Jan 2002 20:20:10 -0000 Received: from laptop.baldwin.cx (root@laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g09KKBK58403; Wed, 9 Jan 2002 12:20:11 -0800 (PST) (envelope-from john@laptop.baldwin.cx) Received: (from john@localhost) by laptop.baldwin.cx (8.11.6/8.11.6) id g09KJbt06178; Wed, 9 Jan 2002 12:19:37 -0800 (PST) (envelope-from john) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 09 Jan 2002 12:19:37 -0800 (PST) From: John Baldwin To: Idar Tollefsen Subject: RE: Using GCC 3 for ports? Cc: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 09-Jan-02 Idar Tollefsen wrote: > John, > >> Don't use gcc 3.0.x. It will dump core on the following code: >> >> switch(foo) { >> default: >> blah(); >> break; >> } >> >> You don't want to know how many places code like this exists in >> our source tree much less in 3rd party software. :) Just make >> sure you have gcc 3.1.x which has this bug fixed. It doesn't look >> like gcc 3.1 is in ports (probably cause there's no released version >> of it yet). However, if you really want to, you can install the >> gcc30 port, and build by doing 'make CC=gcc30'. > > I might hold off until I see 3.1 appear in the port collection then. > > But CC=gcc30 (or 31) is it? What about include paths? Doesn't > 3.x install it's own set of updated libraries, headers, e.g.? Yes, and those paths are compiled into the compiler as its standard include path, just like /usr/include is compiled into /usr/bin/cc as it's standard include path. :) Setting CC is enough, the rest is magic. :) > - IT -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message