From owner-freebsd-current Wed May 27 08:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26961 for freebsd-current-outgoing; Wed, 27 May 1998 08:56:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-100.joh.za.ibm.net [139.92.122.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26956 for ; Wed, 27 May 1998 08:56:22 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id RAA11565; Wed, 27 May 1998 17:51:14 +0200 (SAT) From: Robert Nordier Message-Id: <199805271551.RAA11565@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980527155446.50625@follo.net> from Eivind Eklund at "May 27, 98 03:54:46 pm" To: eivind@yes.no (Eivind Eklund) Date: Wed, 27 May 1998 17:51:11 +0200 (SAT) Cc: 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 Eivind Eklund wrote: > On Wed, May 27, 1998 at 08:15:40AM +0200, Ollivier Robert wrote: > > According to Eivind Eklund: > > > I think making it support e.g. 'long long' would need modifications of > > > the frontend. > > > > lcc, now at 4.0, still has the same problem I think. > > That's basically because "long long" is in total violation of the ISO > standard, IIRC. A type long long int is part of the ISO standard presently under consideration (C9X). It is also not a "total violation" of the current ISO (C89/C94) standard in any meaningful sense. TenDRA can and already does support type long long int. > > I've sent off a mail to the contact person for the TenDRA team; I'll > wait and see that they say about the feasibility of using TenDRA as an > OS compiler. This was the subject of an Open Group research study (involving UnixWare and Linux) around 1995. (Fairly obviously, it is feasible.) 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). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message