This is just a hunch, but...
It sounds as if Borland make and ActiveState Perl are trying to adaptive about which command interpreter they use and now that Cygwin is on your system, they're finding Cygwin's /bin/sh (not BASH but ash, by the way) before they find CMD.exe.
Look at your system's PATH variable and see if it includes your Cygwin bin directory (in it's Windows form, perhaps something like "C:\cygwin\bin") and if it's there, move it after "C:\WINNT\system32".
You might also want to look at the documentation for the errant programs to see if they're configurable in such a way to avoid this pitfall.
Randall Schulz
Mountain View, CA USA
At 11:18 2002-11-07, Jens Schmidt wrote:
Hello,
after installing cygwin I run into the following problem:
All shell commands executed by programs, e.g.
an "echo ************" executed from Borland make or an "open(F_LIST,"dir $ARGV[0] /s /b|");" executed from a Perl script (Activestate)
aren't executed by cmd.exe any more but by bash. The Problem is that bash don't know the commands listed above or behaves in a different way than cmd.exe. It's possible to set a cmd /C for every command, but I have a lot of this stuff and like to use always cmd.exe.
Does somebody know how to disable this redirection to bash ?
Thanks.
Jens
P.S.
comspec is set correct.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
