Date: Wed, 09 Jan 2002 12:19:37 -0800 (PST) From: John Baldwin <jhb@freebsd.org> To: Idar Tollefsen <Idar.Tollefsen@baerum.kommune.no> Cc: freebsd-alpha@freebsd.org Subject: RE: Using GCC 3 for ports? Message-ID: <XFMail.020109121937.jhb@FreeBSD.org> In-Reply-To: <sc3c9f93.060@mail.baerum.kommune.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.020109121937.jhb>