On Mon, Aug 11, 2003 at 04:01:34PM -0400, Jason Tishler wrote:
> Corinna,
>
> On Mon, Aug 11, 2003 at 09:05:39PM +0200, Corinna Vinschen wrote:
> > On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote:
> > > Since the source of ash 20020731-1 seems identical to ash
> > > 20020731-3, this
ash 20020731-3 and/or cygwin 1.5.2 gets confused by a directory and an
executable of the "same" name:
$ mkdir ls
$ cp /usr/bin/ls.exe .
$ sh -c ./ls
./ls: not found
Note this works under (the 32-bit) ash 20020731-1 and cygwin 1.5.2:
$ sh -c ./ls
ls ls.exe
Since the sour
On Mon, Aug 11, 2003 at 10:50:02PM +0200, Corinna Vinschen wrote:
> On Mon, Aug 11, 2003 at 04:01:34PM -0400, Jason Tishler wrote:
> > On Mon, Aug 11, 2003 at 09:05:39PM +0200, Corinna Vinschen wrote:
> > > On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote:
> > > > Since the source of a
Jason Tishler wrote:
Corinna,
On Mon, Aug 11, 2003 at 09:05:39PM +0200, Corinna Vinschen wrote:
On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote:
Since the source of ash 20020731-1 seems identical to ash
20020731-3, this seems to indicate a build and/or cygwin problem...
It's a sit
On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote:
> ash 20020731-3 and/or cygwin 1.5.2 gets confused by a directory and an
> executable of the "same" name:
>
> $ mkdir ls
> $ cp /usr/bin/ls.exe .
> $ sh -c ./ls
> ./ls: not found
>
> Note this works under (the 32-bit)
Corinna,
On Mon, Aug 11, 2003 at 09:05:39PM +0200, Corinna Vinschen wrote:
> On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote:
> > Since the source of ash 20020731-1 seems identical to ash
> > 20020731-3, this seems to indicate a build and/or cygwin problem...
>
> It's a situation wh
6 matches
Mail list logo