X-Spam-Check-By:	sourceware.org
Date:	Thu, 17 Aug 2006 10:29:46 -0400 (EDT)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
cc:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: change in behavior of make from 3.80 to 3.81
In-Reply-To:	<20060817142510.GH20467@calimero.vinschen.de>
Message-ID:	<Pine.GSO.4.63.0608171026540.14156@access1.cims.nyu.edu>
References:	<01b901c6c116$21259430$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816111421 DOT 0b446b60 AT pop DOT nycap DOT rr DOT com> <20060816155054 DOT GY20467 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161418370 DOT 9095 AT access1 DOT cims DOT nyu DOT edu> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816144036 DOT 09695af0 AT pop DOT nycap DOT rr DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161543520 DOT 14156 AT access1 DOT cims DOT nyu DOT edu> <E1GDdoK-0002Ml-Re AT fencepost DOT gnu DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0608170950440 DOT 14156 AT access1 DOT cims DOT nyu DOT edu> <20060817142510 DOT GH20467 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Thu, 17 Aug 2006, Corinna Vinschen wrote:

> On Aug 17 09:59, Igor Peshansky wrote:
> > Actually, as Gareth mentioned, *Cygwin* allows colons in file names on
> > managed mounts.  So, at the very least there'd be confusion of whether
> > c:\\TEMP is a directory TEMP in the root of the C: drive, or a file named
> > 'c:\\TEMP' in the current directory on a managed mount...
>
> Since colons are perfectly valid characters on POSIX file systems,
> there's no reason to generate a special case for Cygwin.  The problems
> generated by using such filenames are identical on all these OSes.

I was simply pointing out that in case of Cygwin, if the build happens to
run on a managed mount (which emulates a true POSIX file system), having
DOS paths in the Makefile is ambiguous anyway.  This is in addition to any
(non-)problems introduced by colons and backslashes.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -