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: Sat, 25 Aug 2001 14:14:20 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Cc: nabbasi AT pacbell DOT net Subject: Re: Problems with path resolution Message-ID: <20010825141420.L21709@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, nabbasi AT pacbell DOT net References: <001d01c12d2f$5c7b93c0$1eea65d8 AT me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <001d01c12d2f$5c7b93c0$1eea65d8@me>; from nabbasi@pacbell.net on Fri, Aug 24, 2001 at 11:29:57PM -0700 On Fri, Aug 24, 2001 at 11:29:57PM -0700, nasser abbasi wrote: >I am also seeing some strange path problems with 1.3.2 > >I say > >ls -l /cygdrive/f/foo > >and it lists it. > >I say > >file /cygdrive/f/foo > >and I get an error 'No such file or directory' > >foo is some binary file. I assume that foo has a .exe extension. ls -l will tack on a .exe to a file name if it can't find it without the extension. ls is probably the only cygwin utility that will do that, with the possible exception of 'cp' (depends on the version of cp and there are bugs in all versions). So, the short answer is 'always add the .exe extension'. 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/