Mail Archives: djgpp/1998/03/30/12:20:09
On Mon, 30 Mar 1998, Andris Pavenis wrote:
> Therefore for building gcc-2.8.1 it is neaded
> to have /bin/sh.exe
I still maintain that this is unneeded. You need sh.exe somewhere on
your PATH, that's all. Setting CONFIG_SHELL=bash and having a line which
says "#!/bin/sh" at the beginning of each shell script should solve the
rest.
> (You can make this by copying bash.exe to
> /bin/sh.exe on the same drive You have gcc sources.
IMHO, this ``solution'' is a Bad Idea. One problem is that you need to
have /bin/sh.exe on *every* drive in the system (there are machines with
a lot of drives). Another problem is that people who have networked
drives will need to copy sh.exe on those also, which is not always
possible. Yet another problem is when you switch to the temporary
directory which is on a RAM disk: a RAM disk is not large enough to waste
it on copies of Bash.
In general, I submit that the DJGPP ports should build on any
garden-variety machine of every John Doe (or Jane Doe, as the case may
be) out there.
- Raw text -