Date: Fri, 29 May 1998 17:22:56 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Eivind Eklund <eivind@yes.no> Cc: joelh@gnu.org, rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Message-ID: <Pine.SV4.3.95.980529171426.4862A-100000@parkplace.cet.co.jp> In-Reply-To: <19980528212713.63593@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 May 1998, Eivind Eklund wrote: > On Thu, May 28, 1998 at 01:29:34PM -0500, Joel Ray Holveck wrote: > > My own concern would be the amount of code in third-party programs > > that uses gccisms. I guess I don't see why we're looking to change. This is an interesting point. I talked Carl Rigney at Livingston recently and their position is that only gcc is supported for their radius distribution. So I submitted patches using __FreeBSD__ consistent with how it was done with other platforms so that radius2.1 will build for FreeBSD out the box using ... make EXT=FreeBSD build Regards, Mike P.S. The Lucent PM3 is a pretty cool box. No more Ascends for me. > Well, here are a couple of points: > * License > * General quality of system (GCC is written under the paradigm 'learn > writing compilers as we go') > * Possibilities for exploiting the cross-CPU nature of XANDF > * Better error checking/control > * Choice (by being able to be compiled with more than one compiler) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.95.980529171426.4862A-100000>