Date: Thu, 26 Sep 1996 08:30:51 +0200 (IST) From: Eli Zaretskii To: Daisuke Aoyama Cc: djgpp-workers AT delorie DOT com Subject: Re: bash 1.14.7 is available In-Reply-To: <199609221739.CAA27066@mars.st.rim.or.jp> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 23 Sep 1996, Daisuke Aoyama wrote: > I put new release and diffs on alpha page. You can get it from: > > http://www.st.rim.or.jp/~jack/alpha/index.html This looks very nice, thanks. I even did a "ln -s bash.exe sh.exe" and now I have `sh' which doesn't blow up into my face every other moment (like the `ms_sh' does). About your port of Make 3.74. (I looked into the diffs to see if maybe I've missed something in my port of 3.75.) What I don't quite understand is the reason for the changes like the following: - #ifndef __MSDOS__ + #if !defined (__MSDOS__) || !defined (USE_COMMAND_COM) Is it because you needed a version of Make that supports a unixy shell (such as `bash')? If so, I suggest to try the latest binary of my port of Make 3.75: ftp://is.elta.co.il/pub/make-375.exe It supports both COMMAND.COM and unixy shells. If the Makefile has a line which says "SHELL=/bin/sh" and you have `sh.exe' anywhere on your $PATH, it will use that as the shell. You can either make `sh.exe' a symlink that actually calls `bash', or override the shell with one of these methods: make SHELL=c:/usr/bin/bash.exe or set MAKESHELL=c:/usr/bin/bash.exe; make If you try the above port and have any comments on how it works in your environment, please let me know, because it will go into DJGPP v2.01 (unless proven terribly buggy).