From:	myknees AT aol DOT com (Myknees)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: sh.exe ???
Date:	28 Mar 1998 19:37:59 GMT
Lines:	31
Message-ID:	<1998032819375901.OAA12999@ladder01.news.aol.com>
NNTP-Posting-Host:	ladder01.news.aol.com
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980326105254 DOT 29215I-100000 AT is>
Organization:	AOL http://www.aol.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <Pine DOT SUN DOT 3 DOT 91 DOT 980326105254 DOT 29215I-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes:

>Subject:	Re: sh.exe ???
>From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
>Date:	Thu, 26 Mar 1998 10:53:42 +0300 (IDT)
>
>
>On 25 Mar 1998, Myknees wrote:
>
>> Some scripts won't run without a "\bin\sh.exe".
>
>I would like to urge everybody who sees cases where "/bin/sh.exe" is
>required to please report them as bugs.  DJGPP ports should work if
>sh.exe is anywhere on your PATH, no explicit /bin directory should be
>required.  So please do NOT assume that these are ``the usual DOS
>hassles''; report them here as bugs.  (Of course, a person who did the
>port can decide that this bug is not serious enough to mandate a fix,
>but that's another story.)

I can't remember whether the specific case was with a djgpp script, but I first
learned of this issue in the readme.djg file of the binutils.  The readme.djg I
have is dated Jul 17, 1997 and says: 
    Because in some scripts and/or makefiles there is a reference
    to /bin/sh, you have to create on the drive, where you have
    unzipped the sources a directory /bin and copy your bash.exe
    in this directory as sh.exe.

...sorry I don't know of a specific case.

--Ed (Myknees)

- Raw text -