From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Problems with file names with Make Date: 10 Mar 2003 22:00:59 GMT Organization: Aachen University of Technology (RWTH) Lines: 30 Message-ID: References: <3i5i6vsg9rgbfbn00p2dna50v1e943ucpf AT 4ax DOT com> <1858-Sat08Mar2003112910+0200-eliz AT elta DOT co DOT il> <4ivp6v8ca47rjdthluimslslvq6smm8b46 AT 4ax DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1047333659 12100 137.226.32.75 (10 Mar 2003 22:00:59 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 10 Mar 2003 22:00:59 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com H Johnson 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.