X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to
	:content-transfer-encoding; q=dns; s=default; b=IEF/qB/bmAsnXDfl
	HpOzsmsd9hBzA/80zwi+ZYcMigYN7Hcyk1g6WK+7kL5kAMcL/zVidGJMq293dBo3
	B9gy+8XHlCriFX19PNuAHPRb+FaEE00PjmMyEUuoiwsXV4dYcAiqap4SDKD3sL16
	DMoA+J1p71mtOOVo7PxYqeh5bRs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to
	:content-transfer-encoding; s=default; bh=5+N+276UAKD1BgTIy+qycm
	4ev5E=; b=Wyn9PXCeD60q6HF0YX5yUWO6M5avS9AXcnBM6b5IOx3XnOP6jWfBn1
	MCR3e+bOqH1cB1Rk/Tf/JHxwdlOmte9i+B4jy66PJq3V3gVXgsXDSavToF1KjmDX
	HVwJCiNFfb3iFbQtFxkJd5pUsZNaR7up57lg7u14gMoV9ZkhkUJPU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SEMBACKSCATTER autolearn=no version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18tEfUUGBjYJlr4Uom+ldJ5
Date: Thu, 1 May 2014 00:45:38 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: make error: *** target =?utf-8?Q?patte?=	=?utf-8?Q?rn_contains_no_`%'=2E_Stop=2E=E2=80=8F?=
Message-ID: <20140501044538.GD1214@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <COL129-W103E1ABFEBCDD360CC6641CB400@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <COL129-W103E1ABFEBCDD360CC6641CB400@phx.gbl>
User-Agent: Mutt/1.5.20 (2009-06-14)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s414jrj3006519

On Wed, Apr 30, 2014 at 07:09:00PM -0700, Richard H. McCullough wrote:
>I picked a bad example, since you don't have my source files.
>The point is this: I've been using Cygwin "make" for years
>and never had a problem.  In the last week, "make" suddenly
>changed -- it does nothing but stop on every makefile.
>
>You must have released a new version of "make" which
>is definitely broken.
>
>Just think about it -- why should "make" suddenly force me to add
>       %: force
>targets for all my existing targets?

As long as we're thinking about it, the last release of make was five
months ago and the mailing list isn't filled with people complaining
that make is broken.

If you can identify a simple example of breakage please send it to
bug-make@gnu.org .

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


