X-Spam-Check-By: sourceware.org
X-BrightmailFiltered: true
X-IronPort-AV: i="4.08,135,1154880000";     d="scan'208"; a="856393805:sNHT17627932"
Message-ID: <44E43673.40007@gmail.com>
Date: Thu, 17 Aug 2006 19:27:15 +1000
From: Gareth Pearce <tilps DOT kilm AT gmail DOT com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: change in behavior of make from 3.80 to 3.81
References: <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060815151104 DOT 0b40e260 AT pop DOT nycap DOT rr DOT com>   <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>
In-Reply-To: <E1GDdoK-0002Ml-Re@fencepost.gnu.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Eli Zaretskii wrote:
> code, perhaps with some Cygwin-specific changes).  Contrary to what
> some people said in this thread, I don't see any problems that could
> hamper the Cygwin build of Make if it supported drive letters, since
> Windows doesn't allow colons anywhere else in file names anyway.  Of
> course, the best way of making sure no problems exist is to test the
> patched version in the Cygwin environment.
>   
I think I read somewhere that you can now have colon's and other such 
characters in filenames in cygwin, you just have to mount the directory 
with a special flag and the filenames you see in windows are encoded.  
So thats a test case for consideration.

--Gareth

--
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/