Mail Archives: djgpp/2001/12/26/11:56:50
> From: big10p AT hotmail DOT com (Chris Chadwick)
> Newsgroups: comp.os.msdos.djgpp
> Date: 26 Dec 2001 07:26:49 -0800
> >
> > You can eat that cake and have it, too: add "SHELL = /bin/sh" line to
> > your Makefile, and Make will invoke Bash to run commands such as the
> > one above. You don't need to make Bash your interactive shell for
> > this to work. (You _do_ need to install the ported Bash, though.)
>
> This was what I was getting at in my OP although I probably didn't
> word it very well. I'm still a bit confused about "SHELL = /bin/sh"
> though: doesn't this make sh.exe the default shell, not bash.exe?
In DJGPP, sh.exe is a ``symlink'' to bash.exe. If you look at
bin/sh.exe on your system, you will see that it's only 2KB long.
That's simply a stub loader which was configured to load the code from
bash.exe.
So you could say "SHELL = /bin/bash" as well, it's just that /bin/sh
is more portable, since some Unix systems don't have Bash.
> Or
> is sh a part of bash? Sorry, but like I said, I'm not familiar with
> all this posix/unix stuff, yet :)
For more about the "SHELL = /bin/sh" magic, read the file README.dos
in the Make distribution (mak3791b.zip).
- Raw text -