Why does declare getopt_long()?

I recently re-ran setup.exe and upgraded the packages I have installed and was surprised to find that many of my projects no longer build with Cygwin. They now fail with an error regarding the redefinition of struct option. These projects use getopt_long() which is of course not portable; so I

getopt() musings

First off, let me state the facts as I understand them: Cygwin's libc provides an implementation of getopt() and getopt_long(). The implementation provided in Cygwin is derived from the NetBSD implementation of getopt_long() witch was in turn designed to be reasonably compatible with GNU getopt

write(2) return codes

o be tools for testing POSIX compliance that might catch some other cases of this, but I don't have any info on that at the moment. Please CC me on any mail, as I'm not on the mailing list. Thanks, David F >From: Steven O'Brien To: "david f" <[EMAIL PROTECTED]

Fwd: write(2) return codes

this problem any more until the read/write bug is fixed. David F >From: "david f" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >CC: [EMAIL PROTECTED] >Subject: write(2) return codes >Date: Wed, 01 May 2002 13:17:01 -0700 > >Hi, > >I've been doing som