Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: Eli Zaretskii , djgpp-workers AT delorie DOT com Date: Tue, 23 Feb 1999 09:51:58 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Bug in make? References: In-reply-to: X-mailer: Pegasus Mail for Windows (v2.54) Reply-To: djgpp-workers AT delorie DOT com Eli Zaretskii wrote: > > 3) The variable should be expanded with forward slashes. > > Every variable or just $(MAKE)? Just $(MAKE), it looks like the second copy of make expands this variable using some strange thing. Why if make is called with $(MAKE) expands with forward slashes and if make is called with "make" expands it with forward slashes? Is very strange. From where comes these forward slashes? argv[0]? DJDIR? > If you mean every variable, I think it's wrong: it will prevent you > from ever having a variable with backslashes. > > But even if you mean to have a special treatment for $(MAKE), I'm not > sure it should be done. Somebody could say something like this: > > command.com /c $(MAKE) > > This won't work with forward slashes. It's a mess... But: 1) Make used a mixed stuff (2 back and one forward!) 2) Make expands this variable in a different way if: a) The second copy was called by make using just make. b) The second copy was called by make using $(MAKE) SET ------------------------------------ 0 -------------------------------- Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(5411) 4759 0013