public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: make error: *** target pattern contains no `%'. Stop.‏
Date: Thu, 01 May 2014 17:50:00 -0000	[thread overview]
Message-ID: <CAJ1FpuPO+pAFj=p_Hg+Vnk=5Mj8hO6K-Srwg4PernN9eMV1-vg@mail.gmail.com> (raw)
In-Reply-To: <536272E0.1010506@towo.net>

On Thu, May 1, 2014 at 10:14 AM, Thomas Wolff <towo@towo.net> wrote:
> Am 01.05.2014 04:09, schrieb Richard H. McCullough:
>>
>> ... In the last week, "make" suddenly
>> changed -- it does nothing but stop on every makefile.
>
> Sounds like you changed your PATH and have a different (non-cygwin) version
> of make now.
> What does `type make` say?
>
> ---
> Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus
> Schutz ist aktiv.
> http://www.avast.com
>

I have seen two things mess up my makefiles in the past.

1) tabs converted to spaces (and vice versa).
2) CRLF instead of LF line separators, or mixed CRLF and LF line separators.

Both of these defects are normally invisible. I have used cat -A or od
-c to help detect these editor induced errors. dos2unix can fix line
endings. An editor with visible whitespace and selectable line endings
options and regexp search and replace can help with fixing tabs.


-- 
Doug Henderson, Calgary, Alberta, Canada

--
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 17:50 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
2014-05-01 16:14 ` Thomas Wolff
2014-05-01 17:50   ` Doug Henderson [this message]
  -- 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='CAJ1FpuPO+pAFj=p_Hg+Vnk=5Mj8hO6K-Srwg4PernN9eMV1-vg@mail.gmail.com' \
    --to=djndnbvg@gmail.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).