delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/12/28/11:53:55

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20011228114355.0231d350@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 28 Dec 2001 11:51:39 -0500
To: "ROHIT X SINGH" <rxsingh AT us DOT ibm DOT com>, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: "no such file or directory" using 'spawn' on EXPECT
In-Reply-To: <OFCF14D12C.8108A195-ON85256B30.005903BC@pok.ibm.com>
Mime-Version: 1.0

At 11:12 AM 12/28/2001, ROHIT X SINGH wrote:

> > Perhaps the output of 'cygcheck -s -r -v' would be of some help (and
> > maybe not! ;-) )
>
>
>Thanks Larry,
>
>I have found something which may be able to pinpoint the source of the
>error: However, I'm not competent enough to judge what's wrong! Perhaps,
>you or someone in the group will be able to help me out...
>
>On the system on which expect's spawn works AS EXPECTED, 'cygcheck -s -r
>-v' reports the PATH as UNIX paths, as follows:...
>
>
>Path: /cygdrive/c/Program Files/ibm/gsk4/lib
>       /cygdrive/c/WINNT/system32
>       /cygdrive/c/WINNT
>       /cygdrive/c/WINNT/System32/Wbem
>       /usr/bin
>       /cygdrive/c/JDK1.3.1_01
>       .
>       .
>       .
>
>
>However, on the system where it DOESN'T Work as expected, the PATH is
>reported as "windows paths, i.e. drive names followed by windows path, as
>follows:
>
>Path: C:\WINNT\system32
>       C:\cygwin\bin
>       C:\WINNT
>       .
>       .
>       .
>
>
>Will this be useful ?



To some extent.  It seems to indicate that you are running different 
versions of the Cygwin package on these different machines.  I have a
machine here running 1.1.8 which reports the path in POSIX form as well.
The other machine, running Cygwin 1.3.6-2, reports DOS-style paths.

Look at the DLL version information at the end of the cygcheck output.
That should confirm this difference.  I'm not sure that this has much
bearing on your problem however.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019