Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<3D15609F.2060403@ece.gatech.edu>
Date:	Sun, 23 Jun 2002 01:46:07 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
CC:	cygwin-developers AT cygwin DOT com
Subject:	Re: release schedule and a problem on getopt_long.
References:	<s1sn0tmh9e5 DOT fsf AT jaist DOT ac DOT jp>

Kazuhiro Fujieda wrote:

> By the way, I seemed to find a problem in getopt_long causing
> a trouble for cygpath and strace. I'm tracking down it now.
> Please wait a moment for the release of 1.3.11.

Speaking of cygwin's getopt implementation, I recently ran in to a 
problem with gettext.  It failed its own selftests when using cygwin's 
implementation, because cygwin's version hardcodes POSIXLY_CORRECT, 
which prevents reordering arguments.  Gettext's test suite depends on 
reordering.

Not really a problem; I simply linked in gettext's copy of the GNU 
version of the getopt functions.  But. I am curious why cygwin's 
implementation forces POSIXLY_CORRECT.  Anybody know?

--Chuck

- Raw text -