From:	jeffdbREMOVETHIS AT goodnet DOT com (Mikey)
Subject:	Re: type command
2 May 1998 06:48:18 -0700 :
Message-ID:	<354a8ca1.3364646.cygnus.gnu-win32@smtp.goodnet.com>
References:	<8B40B8756FA1D111BCB900A02495E24F36B44A AT neptune DOT xstor DOT com>
Reply-To:	jeffdbREMOVETHIS AT goodnet DOT com
Mime-Version:	1.0
To:	gnu-win32 AT cygnus 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 AT cygnus DOT 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 AT goodnet DOT com)
delete REMOVETHIS from the above to reply
         Mikey
-
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 -