X-Spam-Check-By: sourceware.org From: "Gary R. Van Sickle" To: Subject: RE: cygwin unix commands in windows Date: Wed, 4 Oct 2006 23:23:49 -0500 Message-ID: <000301c6e836$0f3ea6c0$020aa8c0@DFW5RB41> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4524727E.1070709@byu.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > From: Eric Blake [snip] > You asked, so I'll answer. Yes, it is an accident that other > tools understand c:/. It's no accident that make used to, and now again will, be supporting Windows paths. People put considerable time and effort into making it work originally, and then again just recently in finally solving the problem and pushing the fix upstream. [snip] > Another example of a program that parses its arguments is > make; you need only read last months archives for the debate > about make 3.80 vs. make > 3.81 for proof that using DOS paths in cygwin programs is > ASKING for problems. I think you're misreading the make issue. Using Windows paths in make was apparently never "asking for problems" until the last release, at which time a problem was introduced, a solution was found, pushed upstream, and the problem is now solved (or will be when the next Cygwin build is released). -- Gary R. Van Sickle -- 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/