> You didn't specify what errors you got when you had the parens in
there
Here you go:
[EMAIL PROTECTED]:~/tmp/make-2006-11-30$ ls -l bracket*
-rw-rw-r-- 1 martind software 0 2006-11-30 16:44 bracket(
-rw-rw-r-- 1 martind software 0 2006-11-30 16:44 bracket()
[EMAIL PROTECTED]:~/tmp/make-2006-11-30$ make 'bracket()'.t
make: *** No rule to make target `bracket().t'. Stop.
[EMAIL PROTECTED]:~/tmp/make-2006-11-30$ make 'bracket('.t
bla bla bla
make: bla: Command not found
make: *** [.bracket(.time] Error 127
[EMAIL PROTECTED]:~/tmp/make-2006-11-30$
Which is to say that I quoted them and got an error from make.
-------------------------------------
Martin's Outlook, BlueArc Engineering
-----Original Message-----
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 18:27
To: Martin Dorey
Cc: Jon Grant; bug-make@gnu.org; Dan Jacobson
Subject: RE: can't get far if file has difficult name
On Thu, 2006-11-30 at 16:52 -0800, Martin Dorey wrote:
> Works for me if I remove the two close-parentheses and replace the
white
> space with underscores. Open-parenthesis fine, close-parenthesis bad.
> Weird. Close-parenthesis is also bad with Debian sarge's make-3.80.
I suspect that has to do with the shell. Although () are not special to
make, they are special to the shell, and make's builtin rules don't
quote their filename arguments (and neither did Dan's example).
You didn't specify what errors you got when you had the parens in there,
but in my tests if I have them (unquoted) I get an error from the shell,
not from make.
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
