X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Colon in dependencies
Date: Wed, 9 Aug 2006 10:45:12 -0400
Message-ID: <467C77F6373BDE4BB16A3E8A62C039555F89CE@Exchserv.hatteras.com>
From: "Brian Hassink" <bhassink AT hatterasnetworks DOT com>
To: <cygwin AT cygwin DOT com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k79EjRsv002342

Thank-you.  This reply was far more helpful than the previous.

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Christopher Faylor
Sent: Wednesday, August 09, 2006 10:17 AM
To: cygwin AT cygwin DOT com
Subject: Re: Colon in dependencies

On Wed, Aug 09, 2006 at 02:10:15PM +0100, Dave Korn wrote:
>On 09 August 2006 13:23, Brian Hassink wrote:
>> From: Rene Nitzsche 
>> Sent: Wednesday, August 09, 2006 8:08 AM
>
>>>how can I use a colon in dependencies for make?  If a dependency
>>>contains a colon, I get the error *** target pattern contains no `%'.
>>>Stop.  I use GNU Make 3.81 for i686-pc-cygwin, GNU bash, version
>>>3.1.17(6)-release (i686-pc-cygwin).  I had search for a solution in
>>>many newsgroups, but I can not found a solution.
>
>>I've run into the same problem after upgrading to 3.81-1 with
>>dependencies that contain a drive letter (e.g., x:\foo\bar.c).
>>
>>For now I've downgraded back to 3.80-1, but would obviously be
>>interested in a better solution.
>
>Before reporting a problem to the mailing list, it's a good idea to a)
>read the release announcement, in case what you think is a problem is
>in fact a by-design feature, and b) search the list archives, in case
>we've been discussing nothing else for the past fortnight and everyone
>is heartily sick of going over the same old ground again.

Yes, what he said.

Also, FYI, I posted two scripts for converting a makefile from c:\foo to
cygwin path format here:

http://cygwin.com/ml/cygwin/2006-07/msg00830.html

cgf

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


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