X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: mwoehlke <mwoehlke AT tibco DOT com>
Subject:  Re: Why are Windows paths broken in make 3.81?
Date:  Fri, 21 Jul 2006 19:34:35 -0500
Lines: 35
Message-ID: <e9rrqr$6ei$1@sea.gmane.org>
References:  <9c2aabaf0607211629u4e29ffa1w5f09b3d8e5a923fc AT mail DOT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
In-Reply-To: <9c2aabaf0607211629u4e29ffa1w5f09b3d8e5a923fc@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

Michael Hirsch wrote:
> Here is a sample Makefile that breaks with Gnu Make 3.81-1 under
> Cygwin, but works fine with Gnu Make 3.80-1.  We have been writing
> these types of Makefiles for years, using both Windows and Cygwin
> tools, and this is the first time Make has ever broken like this.
> 
> I see in another thread that this is a known issue, though I don't see
> it in the changelogs for make 3.81.
> 
> Was this a deliberate break with backwards compatibility?  It means
> that every single reference to a windows path needs to be wrapped in
> cygpath, which is a huge inconvenience.

Yes. See <http://cygwin.com/ml/cygwin-announce/2006-07/msg00008.html>. 
If you are using a POSIX-like "OS" (i.e. Cygwin), you should be using 
POSIX paths. That's not an inconvenience, that's called writing a bad 
makefile. If you aren't using Cygwin for the POSIX environment, you 
should be using MinGW.

> Is it broken only on Windows?

That sounds like a silly question... 'are Windows paths only broken on 
Windows?'

> Is this a cywin only bug?  What possible reason could there be to
> introduce this deliberately?

No, as it is not a "bug". However it is specific to Cygwin. See the 
aforementioned announcement. CGF would have to speak to "why" (and I 
would appreciate if he would, just because I am curious :-)), but I 
would guess it is to "encourage" people to use correct (i.e. POSIX) paths.

-- 
Matthew
Doom doom dooM doo-DooM dOOm DOom doOM... DOOM! -- Gir


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