Subject: Re: Non-ANSI ism in system headers
To: Neil Booth <neil@daikokuya.co.uk>
From: Bill Studenmund <wrstuden@netbsd.org>
List: current-users
Date: 04/25/2005 16:39:08
--KuLpqunXa7jZSBt+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 26, 2005 at 08:19:42AM +0900, Neil Booth wrote:

[snip]

> I'm writing an ANSI C compiler front end, and have yet to implement
> GCC extensions.  It shows exactly the same header trace as
> above, with __signed.  I believe it is NetBSD's intent to have their
> headers compilable with compilers other than GCC?

Not really. We used to, but there are too many places in the code that=20
require gcc extensions.

What you might do is try defining STDC. That should turn off all of the=20
non-gcc (and a lot of non-NetBSD) stuff.

Take care,

Bill

--KuLpqunXa7jZSBt+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFCbX+cWz+3JHUci9cRAndZAJ0eVv669kcT7B/gwrjruWtsz8gIqACZAceg
dAWXvQyhgchwpNduwspAE4U=
=69Lt
-----END PGP SIGNATURE-----

--KuLpqunXa7jZSBt+--