Date:	Tue, 27 Aug 2002 07:54:16 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	JT Williams <jeffw AT darwin DOT sfbr DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: file names in Makefile
In-Reply-To:	<20020826193515.GB24199@kendall.sfbr.org>
Message-ID:	<Pine.SUN.3.91.1020827074959.4522B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 26 Aug 2002, JT Williams wrote:

> FWIW, even Solaris has problems; here is how bash 2.04 under
> Solaris 2.8 reacts to various escape patterns (the file name
> is "2000;64(4):349--362.pdf").
> 
> % ls ~/docs/2000;64(4):349--362.pdf
> bash: syntax error near unexpected token `;64(4)'
> 
> % ls ~/docs/2000\;64(4):349--362.pdf
> bash: syntax error near unexpected token `;64(4'

That's from Bash command line; that's a (slightly) different story.  
Let's stick to Make for a moment and turn to Bash later, shall we?

Is it true that 2000\;64(4)\:349--362.pdf works on Solaris in the sample
Makefile you posted at the beginning of this thread, if you use GNU Make 
there?  If it doesn't work, what error messages do you get?

> % ls ~/docs/2000\;64(4):349--362.pdf
> bash: syntax error near unexpected token `;64(4'

Shell commands _do_ need to quote parentheses.  But that's easy to add 
once we have the Make problems figured out.

> _None_ of these escape patterns, with or without quotes,
> is acceptable inside a Makefile (with make 3.78.1).

Can you try the latest Make 3.79.1?  Did you use 3.78.1 in the DJGPP case 
as well?  If so, please try the latest binary in all cases, I think this 
particular issue got several bugfixes.

- Raw text -