Date: Sun, 27 Oct 1996 15:13:21 +0200 (IST) From: Eli Zaretskii To: "Alaric B. Williams" Cc: djgpp AT delorie DOT com, DJ Delorie Subject: Re: Compiling GCC 2.7.2.1 with itself In-Reply-To: <846360417.8962.0@abwillms.demon.co.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 26 Oct 1996, Alaric B. Williams wrote: > I've got the new V2.01 make, and I think it's a Little Bit Different. It's A Lot Different :-) > A) It won't run the gen* executables unless I add '.' to the path. > Luckily, I knew enough of Unixisms to think of trying that. > > B) A mysterious entity called 'sh' produces warnings something like > so: > > gensomething < ./something.def > something.c > sh: Filename <.something.def> contains too many periods, changing to > <~something.def> Do you have a program named `sh.exe' somewhere on your PATH? And if so, does the Makefile you use say "SHELL=/bin/sh"? If the answer to both these questions is `yes', then the new Make calls that shell for any command that includes shell-specific features like redirection or pipes. Just say "make SHELL=c:/dos/command.com ..." (or wherever your COMMAND.COM resides) and get back the previous behavior. All this (and much more) is explained in the file README.dos included in the source distribution; it should have been included in the binary distribution also. (DJ, can you please include it in the future binary distributions of Make? Thanks.) For now, download mak375s.zip and read that file carefully.