From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10996 invoked by alias); 26 Sep 2003 05:44:49 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 10962 invoked from network); 26 Sep 2003 05:44:48 -0000 Received: from unknown (HELO booch.minidns.net) (67.160.219.187) by sources.redhat.com with SMTP; 26 Sep 2003 05:44:48 -0000 Received: from [127.0.0.1] (helo=dessent.net) by booch.minidns.net with esmtp (Exim 4.22) id HLT3YL-0001O8-CQ for cygwin@cygwin.com; Thu, 25 Sep 2003 22:44:45 -0700 Message-ID: <3F73D24C.A6F8E92@dessent.net> Date: Fri, 26 Sep 2003 06:21:00 -0000 From: Brian Dessent Organization: My own little world... X-Accept-Language: en,en-US MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Error while running a .exe file in bash References: <20030926052107.62405.qmail@web9802.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg01667.txt.bz2 Kishen Bahudhanam wrote: > > Thanks to everyone who contributed to this issue. The > problem is resolved if I use: ./tx.exe. > I still don't understand the error message though. > If bash is not able to find the program, then filename > completion shouldn't work, isn't it? For example if I > just type: > >. t > bash completes the file name to tx.exe (this is the > only executable in the current directory starting with > t). > > To make it actually run, I need to type: > >./tx.exe Typing ". file" at a bash prompt means "read the file and execute the commands stored within", which means bash will open the file and try to execute its contents as if you'd typed them at the prompt. That is NOT what you want for an .EXE file, it only works for shell scripts. To run a normal executable you just give its name and bash runs it. In the case of an executable in the current directory, this is normally not in the path and so you need to specify "./file" to tell bash to look in the current directory which is ".". Those are two completely different uses of "." though. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/