public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: make error: *** target pattern contains no `%'. Stop.‏
Date: Thu, 01 May 2014 04:45:00 -0000	[thread overview]
Message-ID: <20140501044538.GD1214@ednor.casa.cgf.cx> (raw)
In-Reply-To: <COL129-W103E1ABFEBCDD360CC6641CB400@phx.gbl>

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

  reply	other threads:[~2014-05-01  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01  2:09 Richard H. McCullough
2014-05-01  4:45 ` Christopher Faylor [this message]
2014-05-01 16:14 ` Thomas Wolff
2014-05-01 17:50   ` Doug Henderson
  -- strict thread matches above, loose matches on Subject: below --
2014-04-30 17:13 Richard H. McCullough
2014-04-30 17:31 ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140501044538.GD1214@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).