From owner-freebsd-current Thu May 28 12:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01378 for freebsd-current-outgoing; Thu, 28 May 1998 12:12:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-118.joh.za.ibm.net [139.92.122.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01215 for ; Thu, 28 May 1998 12:12:05 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id VAA26880; Thu, 28 May 1998 21:05:44 +0200 (SAT) From: Robert Nordier Message-Id: <199805281905.VAA26880@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805281829.NAA01253@detlev.UUCP> from Joel Ray Holveck at "May 28, 98 01:29:34 pm" To: joelh@gnu.org Date: Thu, 28 May 1998 21:05:42 +0200 (SAT) Cc: rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > > The critical issue, however, is really whether it is feasible to > > compile *FreeBSD* with a non-GCC compiler. Any real problems will > > be due to FreeBSD (GCC quirks in the code) not to the compiler. > > (There are no fundamental difficulties inherent in compiling > > UNIX-like systems). > > 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. A reasonable point. TenDRA does have a more relaxed mode, but there are various things it can't handle. For instance, using cast expressions as lvalues (perhaps that's a pc-ism). I only want to be *able* to change: If you love gcc, let it go. If it stays, it is suitable If not, it never was. 8-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message