Mail Archives: djgpp/1997/02/19/07:20:13
On 19 Feb 97 at 11:23, Eli Zaretskii wrote:
>
> On Wed, 19 Feb 1997, Vyacheslav O. Myskin wrote:
>
> > But it makes impossible to use rm -f somedir/* in makefiles, which is
> > much worse.
>
> No, the above command will work perfectly in a Makefile, because Make
> calls `system' when it sees a wildcard (or any other character special to
> the shell). Btw, that is exactly how Make works on Unix: when it sees a
> wildcard, it calls the shell to do the job instead of calling `execXX'.
>
> (In general, you should try things before complaining that they don't
> work.)
I started complaining AFTER things didn't work.
-----------------------------------------------
Directory of D:\TMP
. <DIR> 02-03-97 8:08p
.. <DIR> 02-03-97 8:08p
DIR1 <DIR> 02-19-97 5:15p
MAKEFILE 18 02-19-97 5:17p
----------------------------------------------
Directory of D:\TMP\DIR1
. <DIR> 02-19-97 5:15p
.. <DIR> 02-19-97 5:15p
PLOT CC 3,180 02-17-97 10:47p
PTEST CC 1,347 02-16-97 4:45p
UTILS CC 2,405 02-13-97 7:42p
DIR1 0 02-19-97 5:19p
----------------------------------------------
The makefile:
all:
rm dir1/*
-----------------------------------------------
Starting make from d:\tmp
-----------------------------------------------
D:\TMP>make
rm dir1/*
c:/djgpp/bin/rm: dir1/*: No such file or directory (ENOENT)
make.exe: *** [all] Error 1
------------------------------------------------
Nothing changes in d:\tmp\dir1
Typing at DOS prompt:
------------------------------------------------
D:\TMP>rm dir1/*
D:\TMP>
------------------------------------------------
d:\tmp\dir1 is empty now. -f just suppresses the error message,
all the rest is the same.
-
______________________________________________
Vyacheslav O. Myskin <myskin AT inp DOT nsk DOT su>
Budker Institute of Nuclear Physics (BINP RAS)
Novosibirsk, Russia
- Raw text -