Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3A92B6BC.A243B41F@yahoo.com>
Date: Tue, 20 Feb 2001 13:26:04 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-apps AT cygwin DOT com
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jason Tishler <Jason DOT Tishler AT dothill DOT com>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: ash's handling of foo.exe and Foo (Re: Cygwin 1.1.8 Python 2.1a2 
 Builds OOTB)
References: <20010220120035 DOT E512 AT dothill DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jason Tishler wrote:
> 
> On Mon, Feb 20, 2001 at 10:57:53AM -0500, Jason Tishler wrote:
> > On Mon, Feb 05, 2001 at 12:44:09PM -0500, Jason Tishler wrote:
> > > Python 2.1a2 builds OOTB under Cygwin 1.1.8 or later.
> >
> > There is one nit that I just noticed -- make install will fail during
> > the $(srcdir)/Lib/$(PLATDIR) target.  The simple workaround is to execute
> > make install as follows:
> >
> >     make EXE=.exe install
> >
> > I will submit a patch to Python to correct the above problem which can be
> > traced to the Makefile is now using EXEEXT while the regen shell script is
> > still using EXE.  But, this could also be classified as an ash "issue" so
> > see my next post, if interested.
> 
> Although, this could be corrected in ash too.  It seems like ash won't
> execute foo.exe when there also exists a directory called Foo at the
> same level:
> 
>     $ sh
>     $ ls -dl [Pp]ython*
>     drwxr-xr-x   3 jt       Domain U    24576 Feb 19 16:12 Python
>     -rwxr-xr-x   1 jt       Domain U    34903 Feb 19 16:13 python.exe
>     $ python
>     python: not found
>     $ python.exe
>     Python 2.1a2 (#1, Feb 19 2001, 16:13:17)
>     ...
> 
> But, the above problem does not occur in bash:
> 
>     $ bash
>     $ ls -dl [Pp]ython*
>     drwxr-xr-x   3 jt       Domain U    24576 Feb 19 16:12 Python
>     -rwxr-xr-x   1 jt       Domain U    34903 Feb 19 16:13 python.exe
>     $ python
>     Python 2.1a2 (#1, Feb 19 2001, 16:13:17)
>     ...
> 

Hmm...  Interesting.  The autoconf maintainers have been having a nice
go with this too.  Bashes builtin `test' command will find the directory
python first.  Such that `test -x python && test -f python' will return
false.  Having a directory and an executable of the same name will break
autoconf in finding the executable.  The suggested workaround is "don't
do that".

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com