From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4808
Path: main.gmane.org!not-for-mail
From: antos@math.muni.cz (David Antos)
Newsgroups: gmane.comp.tex.context
Subject: Re: make files
Date: Sat, 9 Jun 2001 11:35:14 +0200 (CEST)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20010609093514.0D5C852352@bart.math.muni.cz>
References: <3.0.6.32.20010608113628.00aab850@server-1>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035395447 28914 80.91.224.250 (23 Oct 2002 17:50:47 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 17:50:47 +0000 (UTC)
Cc: ntg-context@ntg.nl
In-Reply-To: <3.0.6.32.20010608113628.00aab850@server-1> from Hans Hagen at "Jun
	8, 2001 11:36:28 am"
Original-To: Hans Hagen <pragma@wxs.nl>
Xref: main.gmane.org gmane.comp.tex.context:4808
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4808

> >The colon (:) *must* follow the target (e.g. no spaces), and the execution
> >line(s) must be preceeded by a tab (Ctrl+I, ASCII 9) character.
>  
> That works, is this windows specific or does the linux make also need that
> <tab> char? [i hate tabs]
> 
The <tab> syntax is make-specific. It is very very supid. The GNU make
only adds some types of rules to ``standard'' make (e.g., some kind of
`wildcards', more comfortable ways to handle filenames). Nevertheless
the <tab> syntax will survive everything.

				D.A.

P.S.: Some `too-inteligent' text editors convert your tabs into spaces
(and the user doesn't know that option is set). If your Makefile doesn't 
want to work and there is no reason why, check this.
It happened to me...