X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <2ca21dcc0901021504r18c1cbefoa05f515cfbc5ba09@mail.gmail.com>
Date: Fri, 2 Jan 2009 23:04:28 +0000
From: "Dave Korn" <dave DOT korn DOT cygwin AT googlemail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cmd.exe from Cygwin
In-Reply-To: <5195c8760901020359y51dbe19cw2803e36afe028c1d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5195c8760901020359y51dbe19cw2803e36afe028c1d AT mail DOT gmail DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Jeenu V wrote:

> The program I intend to run with cmd.exe (with /c switch) fails to run
> as it couldn't access some Windows paths. Please take a look like this
> command, for example:
>
> N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\test>cmd /c
> bldmake bldfiles ARMV6
> sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat:
> command not found
>
> There are two things that I'm surprised about:
> 1) How come a command launched from cmd.exe spits an error message
> starting with 'sh:'?
> 2) Why are back-slashes stripped-off from the path in output message?

  My WAG: You're using some kind of embedded toolchain for Symbian that is
based on the gnu tools, and there's some kind of PATH-clash going on between
those and the Cygwin versions.  Maybe it shipped with a mingw32-ish sh.exe
that it's trying to invoke and your Cygwin sh.exe is getting in there first?
We'll need to see your cygcheck output (as described at
http://cygwin.com/problems.html, please take special note of the request to
send it as an attachment rather than inline body text, TIA) to get an idea if
that's happening.

> Also it came to my notice that cmd.exe invoked from a Cygwin bash
> shell doesn't really behave like the Windows cmd.exe. For example, if
> you press up-arrow, the cursor goes flying over the window and the
> display sometimes goes for a toss. Keys like F7 and F8 doesn't work
> either.
>
> It would suffice--as of now, at least--if I could launch a
> cmd.exe--separate and independent--window from a Cygwin shell. I could
> try
>
> explorer.exe c:\windows\system32\cmd.exe
>
> but I'm unable to pass parameters to cmd.exe (say /c or a batch file name).

  That's bizarre but could be related.  For me, just invoking cmd.exe
directly at a Cygwin prompt works fine.

~ $ cmd.exe /c echo "foo"
foo
~ $

  If I want a separate shell, "cygstart cmd.exe" launches it in its own
console window.  Are you running in a console (DOS) window or a terminal such
as rxvt?  It'll only work well in a console.

    cheers,
      DaveK

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/