From: mdruiter AT cs DOT vu DOT nl (Ruiter de M) Newsgroups: comp.os.msdos.djgpp Subject: Re: MAKE with BASH Date: 29 May 1998 12:59:04 GMT Organization: Fac. Wiskunde & Informatica, VU, Amsterdam Lines: 28 Message-ID: <6kmbeo$j7i$1@star.cs.vu.nl> References: NNTP-Posting-Host: sloep54.cs.vu.nl To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote: > On 27 May 1998, Ruiter de M wrote: > > autoconf/configure put INSTALL=//j/bin/ginstall.exe in all makefiles. > Either set INSTALL=${DJDIR}/bin/ginstall in the environment before > running the scripts, or modify the script to call echo.exe (must use > the .exe suffix) where it puts the value of INSTALL in these files. I knew about that solution, but I hoped there would be a more elegant way, like letting Make know about //d/dir/file. > > Yes, I read the info there. But I noticed that setting MAKESHELL=bash > > had some strange side effects. I didn't consider it worthwile to post > > a question abut it, just put SHELL=/bin/sh in my makefile instead. > If you set MAKESHELL or SHELL in the environment, you are expected to > include a full pathname and extension, like in > MAKESHELL=c:/bin/bash.exe. Otherwise it won't work. This should be > explained in the docs and README. Aha, including extension! I think that's the reason of my problems. Thanks for your help. -- Groeten, Michel. http://www.cs.vu.nl/~mdruiter ____________ \ /====\ / "You know, Beavis, you need things that suck, \/ \/ to have things that are cool", Butt-Head.