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 User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: change in behavior of make from 3.80 to 3.81 References: <6.2.3.4.2.20060815151104.0b40e260@pop.nycap.rr.com> <01b901c6c116$21259430$a501a8c0@CAM.ARTIMI.COM> <6.2.3.4.2.20060816091525.0ab90af0@pop.nycap.rr.com> <20060816144110.GX20467@calimero.vinschen.de> <6.2.3.4.2.20060816111421.0b446b60@pop.nycap.rr.com> <20060816155054.GY20467@calimero.vinschen.de> <6.2.3.4.2.20060816144036.09695af0@pop.nycap.rr.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/