Mail Archives: djgpp/2003/03/10/17:15:04
H Johnson <classy-kg4wou AT kg4wou DOT com> wrote:
> So my guess would be that whatever code in COMMAND.COM that the "for"
> command executes is not parsing the string properly and passing
> whatever program is being called a bogus file name.
That may well be the case. So you may have to stop using COMMAND.COM
as the shell to execute commands from within your makefile. The DJGPP
port of GNU make works very nicely with the DJGPP port of GNU Bash,
which is a lot more comfortable with / than command.com. It's also a
_lot_ more powerful than that sorry excuse for a command line shell MS
left you stuck with.
> While not trying it yet, my guess is that using a DJGPP port of RM
> will not fix the problem.
It will --- by removing the need for that 'for' loop altogether.
rm.exe knows how to deal with more than one file at a time, so you can
just call, e.g.
rm -f $(OBJS)
and that's that.
As to the problems regarding nasm, DJGPP's bash as the SHELL for your
makefiles will almost certainly solve those for you, too. Not
automagically, sometimes, but it'll fit in better than command.com.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -