Date:	Mon, 23 Mar 1998 10:15:15 +0200 (EET)
From:	Andris Pavenis <pavenis AT latnet DOT lv>
To:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>,
	djgpp AT delorie DOT com, pavenis AT laima DOT acad DOT latnet DOT lv
Subject:	Re: Building gcc-2.8.1 for DJGPP
In-Reply-To:	<35157C9D.C6E2E6DA@gmx.net>
Message-ID:	<Pine.GSO.3.96.980323101038.7396A-100000@sisenis>
MIME-Version:	1.0

On Sun, 22 Mar 1998, 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:
> 
> O:\TMP>cat test
> /bin/sh test1
> 
> O:\TMP>cat test1
> echo hello
> 
> O:\TMP>bash test
> test: /bin/sh: No such file or directory (ENOENT)
> 
> O:\TMP>

It didn't work also for mi. I have sh.exe ( ln -s bash.exe sh.exe) in
C:/DJGPP/BIN which is on path. Anyway configure script for gcc-2.8.1
didn't run for me before I did one of things:
1) edit configure and replace CONFIG_SHELL=/bin/sh to /djgpp/bin/sh.exe
   I'm not very like this way. So I prefer one suggested by Robert (2)
2) have sh.exe in /bin

Andris

- Raw text -