Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	N8TM AT aol DOT com
Message-ID:	<af749ad5.37002be2@aol.com>
Date:	Mon, 29 Mar 1999 20:41:54 EST
To:	Charles DOT Gauthier AT iit DOT nrc DOT ca
Cc:	pof AT uvic DOT ca, cygwin AT sourceware DOT cygnus DOT com
Mime-Version:	1.0
Subject:	Re: problem building egcs-1.1.2
X-Mailer:	AOL 4.0 for Windows 95 sub 238

In a message dated 3/29/99 6:34:25 AM Pacific Standard Time,
Charles DOT Gauthier AT iit DOT nrc DOT ca writes:

> So far, I only found that the expect interpreter has the pathname problem. 
> All
>  other cygwin tools appear ok. //<drive letter>/ did not work either. It had
> to be
>  a relative path, or start with a dirver letter and colon.
Some of the cygwin snapshots, begining with the Jan. 23 version, gave me this
problem with not recognizing //d, requiring either d: or not working at all
with drive designation, however the Mar. 8 snapshot has cured this.  Its main
annoying feature is the continual warning about losing track of a job numbered
something like 2^31.  The last 2 snapshots refused to run tar, so I backed
them out.  For the time being, I've also backed out my installation of
make-3.77, as the Mar. 8 snapshot seems to do OK with its own version of make.

I tried copying egcs testsuite to drive C: on my NT box today (standard
cygwin-b20.1) and it does sometimes see successful executions not seen when
reading from //d.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -