X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<49A7F037.6060609@gmail.com>
Date:	Fri, 27 Feb 2009 13:52:55 +0000
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: problem with make-3.81
References:	<cf666de870340244cc034e8382e89ae6 AT freesurf DOT fr>
In-Reply-To:	<cf666de870340244cc034e8382e89ae6@freesurf.fr>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

ycollet wrote:

> I was trying to compile project from coin-or (http://www.coin-or.org) using
> the cygwin tools and I found a problem: 
> .deps/ClpCholeskyBase.Plo:1: *** multiple target patterns. (and several
> other error messages from this kind) 
> 
> So I searched in google some hints and found that this is a "well know"
> problem. It seems that make 3.81 has some difficulties to handle "automatic
> header file dependencies". 

  No, not exactly.  Make handles automatic header file dependencies absolutely
fine, but the one thing it doesn't understand is DOS-style paths that begin
with a drive letter and colon.  So if you're using a non-cygwin compiler that
outputs the wrong kind of file paths, make won't understand them.

> PS: I added the comment made on the coin-or website related to this problem
> with reference to the bug description (see the 2006 year ...).

  That's not helpful, because you misunderstood and your comment is incorrect
and misleading.  The real problem (I can tell without even looking at the site
or anything else) is that you are using the cygwin compiler's "-mno-cygwin"
option, which in fact turns it into a MinGW compiler, using DOS-based file
paths.  If you want make to understand MinGW paths generated by a MinGW
compiler, you should use a MinGW make, not a Cygwin make.

    cheers,
      DaveK

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