Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
From: dave DOT banham AT tde DOT alstom DOT com
To: cygwin AT sourceware DOT cygnus DOT com
Message-ID: <C1256973.005E7E0D.00@mz02world.hq.dtr.gecalsthom.fr>
Date: Mon, 9 Oct 2000 16:47:36 +0100
Subject: BUG: Invalid assumption about file paths beginning with '\'
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline


Cygwin version B18 (I think!)

I am using the CygWin GAWK program and have been trying to use absolute path
names for both the script file and input file. I find that I can only used
absolute paths if they start with a drive letter. After some rooting through the
documentation I found that CygWin maps Windows paths to POSIX paths by
converting the drive letter to a folder name. The trouble begins when the drive
letter is missing.

The default 'mount' for '\' is 'c:\', so my absolute paths that don't have a
drive letter are taken as being on drive c: rather than on the current working
drive.

OK, so I could change the mount for '\' to whatever drive I am using.
Unfortunately, I can't because I am using gawk inside a makefile that can be run
on a networked drive mounted as an arbitrary drive letter by any number of
users. (If I could get the current working drive letter into a makefile macro I
could solve the problem by an other means, but I can't and, in any respect, the
problem reveals an assumption in CygWin's DOS\Windows path mapping to POSIX.)

Please consider changing the CygWin file path mapping schema to utilise the
current working drive rather than a default.

Best Regards
Dave Banham

PS I am not on the e-mail list, so please copy to me any useful remarks.


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