This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: type command
- To: gnu-win32 at cygnus dot com
- Subject: Re: type command
- From: jeffdbREMOVETHIS at goodnet dot com (Mikey)
- Date: Sat, 02 May 1998 03:05:02 GMT
- Organization: Never
- References: <8B40B8756FA1D111BCB900A02495E24F36B44A@neptune.xstor.com> <199805010944.KAA29858@zaphod.long.harlequin.co.uk>
- Reply-To: jeffdbREMOVETHIS at goodnet dot com
On Fri, 1 May 1998 10:44:44 +0100, you wrote:
>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?
Incorrect, ash.exe is the only /bin/sh that will work under win95
to configure/compile the CDK
/bin/sh == bash.exe crashes 95
so does make check in the ...src/bash dir of the CDK
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
=====================================================
Linux a platform built by, and for users, standing on
the firm legs of reliability, and speed.
Microsoft Windows, a platform without a leg to stand on.
(jeffdbREMOVETHIS@goodnet.com)
delete REMOVETHIS from the above to reply
Mikey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".