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: Chris Faylor Date: Mon, 29 Mar 1999 22:24:38 -0500 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: problem building egcs-1.1.2 Message-ID: <19990329222438.B2607@cygnus.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from N8TM@aol.com on Mon, Mar 29, 1999 at 08:41:54PM -0500 On Mon, Mar 29, 1999 at 08:41:54PM -0500, N8TM AT aol DOT com wrote: >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. /// 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. Are you submitting bug reports on the snapshots? If so these are not adequate. I don't know what "refused to run tar" means, for example. As far as the snapshots not interpreting //d correctly, please be advised that this "feature" will be deprecated in the next release. It will still work, but the new way to access drives will be via a new mechanism: /cygdrive/d . -dhris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com