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
Date: Wed, 23 Jun 1999 23:17:59 -0400
From: Christopher Faylor <cygwin AT sourceware DOT cygnus DOT com>
To: Robert Bresner <rbresner AT olf DOT com>
Cc: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Another clue into my problem with make...
Message-ID: <19990623231759.C9161@cygnus.com>
References: <37714E16 DOT 69EF8DAE AT olf DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <37714E16.69EF8DAE@olf.com>; from Robert Bresner on Wed, Jun 23, 1999 at 05:13:58PM -0400

On Wed, Jun 23, 1999 at 05:13:58PM -0400, Robert Bresner wrote:
>	2. Before, the PATH was getting _blown away_ [ PATH=(null) ],
>	but I've now seen where an NT style path (e.g. w:\my_path)
>	is being changed to a *nix style path, after an NT mount
>	(e.g. //w/my_path). That is just incredibly odd. Does 
>	GNU make check the Cygwin mount table? 

Any cygwin application changes the path from MS-DOS format to UNIX
format automatically, so this is not surprising.

Sorry, but I have no other insight into your problem.  The translation
to POSIX format is not surprising, though.

cgf	

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