Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sun, 23 Jun 2002 14:45:14 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: release schedule and a problem on getopt_long. Message-ID: <20020623184514.GA17839@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers 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 Sun, Jun 23, 2002 at 06:21:41PM +0900, Kazuhiro Fujieda wrote: >>>> On 23 Jun 2002 14:05:54 +0900 >>>> Kazuhiro Fujieda said: > >> 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. > >This trouble was caused by my fault. > >The trouble was that I wasn't able to feed arguments to cygpath >and strace when they were installed in /bin. I jumped to the >wrong idea that there were some problems in getopt. > >I've forgotten I set the `cygexec' flag to /bin and /usr/bin in >my mount table a few weeks ago, sigh. Argh. I've done that myself. It's a problem. This is one reason why I don't always recommend setting cygexec. However, I think this should be a problem only for strace.exe and cygcheck.exe. I don't see why cygpath should be affected. cgf