From:	jont AT harlequin DOT co DOT uk (Jon Thackray)
Subject:	RE: type command
1 May 1998 07:56:56 -0700 :
Message-ID:	<199805010944.KAA29858.cygnus.gnu-win32@zaphod.long.harlequin.co.uk>
References:	<8B40B8756FA1D111BCB900A02495E24F36B44A AT neptune DOT xstor DOT com>
To:	gnu-win32 AT cygnus DOT com

Bob McGowan writes:
 > In b19, the sh.exe is a different shell, based on something called ash.
 > It does not support the shell built-in command "type" (to check, run
 > "sh"
 > from the bash command line, then put in the command "type type".  The
 > ash
 > shell generates the output "type: not found" while bash says "type is a
 > shell builtin").  The make is probably running "sh" so if it is actually
 > ash then you have problems.  Rename sh.exe to ash.exe (if you want to
 > keep
 > it), then copy bash.exe to sh.exe.  Hopefully this will fix the problem.

Given that ash.exe is no use for commands like make, is there a good
reason why sh.exe, which one is recommended to copy into /bin so that
it is available for make, is actually ash.exe, which is no use for
make?
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -