include incompatibilities

Chris Faylor
Thu Jun 29 15:20:00 GMT 2000

On Thu, Jun 29, 2000 at 11:22:45PM +0200, wrote:
>I had lamented about incompatible changes in include files.
>May I repeat the practical essence of my previous mail which is the 
>question: How can these things be detected by #ifdef's without 
>referring to actual system specifics as below?
>#include <errno.h>
>#ifdef __CYGWIN__	/* and version > something ... ! */
>#define sys_nerr _sys_nerr
>#define sys_errlist _sys_errlist
>(On "classical" systems, the exported names are without underlines - 
>why do these name manglings have to be imposed on us?)

I guess "classical" systems does not include linux.

You're talking about normal problems with porting software between various
systems.  This kind of thing is a fact of life that you have to live with.

It's the reason for things like autoconf and MetaConfig.  Perhaps using
one of those two packages is the solution you're straining for.


Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list