Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 28 Nov 2001 20:29:28 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: which getopt.c is cygwin1.dll using? Message-ID: <20011129012928.GB10485@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Wed, Nov 28, 2001 at 05:26:24PM -0800, Downey, Nathan wrote: >Distantly related to this is a problem that I had recently. I wanted to >compile pdksh-5.2.14 for cygwin. The only problem I have was a namespace >conflict with getopt.h. Its seems that pdksh define a struct called "struct >option" in the source, this is also defined in getopt.h this wouldnt have >been a problem becuase pdksh doesnt use getopt for command line parsing, but >it does include , after looking at the definition of I >noticed that under cygwin include . According to the >POSIX spec is not supposed to include , as a work >around I redifed the local variable to "struct option_local"..... thought I >would bring it up hopefully a develope can comment on whey cygwin does this? The usual answer: Because we're mean. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/