Date: Sun, 22 Mar 1998 21:53:51 -0800 (PST) Message-Id: <199803230553.VAA24551@adit.ap.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Robert Hoehne , Eli Zaretskii From: Nate Eldredge Subject: Re: Building gcc-2.8.1 for DJGPP Cc: "Salvador Eduardo Tropea (SET)" , djgpp AT delorie DOT com, pavenis AT laima DOT acad DOT latnet DOT lv Precedence: bulk At 10:03 3/22/1998 +0100, Robert Hoehne wrote: >Eli Zaretskii wrote : >> >> You do NOT need sh.exe in /bin, you can have it in *any* directory on >> your PATH. Both Make and Bash will find it and invoke it whenever a >> script or a Makefile calls for "/bin/sh". > >Are you sure? I tried it now with the following two files >which are located in o:/tmp and the directory o:/bin does >not exist (and so also no /bin/sh). Here is screen copy: [deleted] AFAIK the part about it not having to be in /bin applies only when it's a shell interpreter line. It should work if your script is like: #! /bin/sh echo Hello Nate Eldredge eldredge AT ap DOT net