From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Philippe Bastiani <philippe.bastiani@wanadoo.fr>
Cc: cygwin@cygwin.com
Subject: Re: Problem with make 'undef missing'
Date: Sat, 06 Sep 2003 19:26:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309061525110.7348@slinky.cs.nyu.edu> (raw)
In-Reply-To: <bjd6q2$371$1@sea.gmane.org>
On Sat, 6 Sep 2003, Philippe Bastiani wrote:
> Hi,
>
> I use a generic makefile on several systems... In the past, this makefile
> worked fine under Cygwin !
> Now, I obtain the following error: 'makefile.def:3: *** <endef> missing...
>
> See, the following stupid makefile:
> *** Begin of file ***
> ifneq ($(strip $(SUBDIRS)),)
> else
> <TAB>define MAKE_SUBDIRS
> <TAB><TAB>$(MAKE_NOTHING)
> <TAB>endef
> endif
>
> .PHONY : all
> all : depend
>
> .PHONY : depend
> depend depends: $(CCLIST) $(CLIST)
> $(MAKE_DEPENDS)
> $(MAKE_SUBDIRS)
> *** end of file ***
>
> Please note: if I replace the <TAB> character (line 5, before the endef) by
> blank characters.. make works with no error !
>
> a+
Philippe,
This was reported before (quite recently, maybe in the past couple of
months). I don't recall the exact details or whether there was a
resolution, but you should be able to find it in the archives. Sorry I
couldn't me more helpful.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
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/
prev parent reply other threads:[~2003-09-06 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 17:51 Philippe Bastiani
2003-09-06 19:26 ` Igor Pechtchanski [this message]
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=Pine.GSO.4.56.0309061525110.7348@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin@cygwin.com \
--cc=philippe.bastiani@wanadoo.fr \
/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).