From:	mdruiter AT cs DOT vu DOT nl (Ruiter de M)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: MAKE with BASH
Date:	27 May 1998 13:26:05 GMT
Organization:	Fac. Wiskunde & Informatica, VU, Amsterdam
Lines:	46
Message-ID:	<6kh49d$a6a$1@star.cs.vu.nl>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980526191816 DOT 20866G-100000 AT is>
NNTP-Posting-Host:	galjas.cs.vu.nl
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
> > I hate it when, for instance, configure figures out that
> > //j/bin/ginstall.exe is my GNU-install and Make fails to run it
> > (because it doesn't know about the //d/* Bash extension).

> You shouldn't need to struggle with these problems in the first place.
> If you set PATH_SEPARATOR=:, always set PATH_EXPAND=y as well.  This
> will cause Bash to convert the pathnames back to the usual DOS
> d:/foo/bar form when it invokes external program (make.exe is an
> external program).

Yes, I have set PATH_EXPAND=y too. I don't know exactly when and where
it happend (my memory is suffering from Windows-bloat I think :), but
autoconf/configure put INSTALL=//j/bin/ginstall.exe in all makefiles.

> The //d/foo feature and PATH_SEPARATOR=: are only designed to make
> Unix shell scripts which take PATH apart work.

That's what I used it for, with `configure' after autoconf-ing.

> > I noticed the MAKESHELL-variable somewhere. Just what does it do
> > _exactly_?

> It has the same effect as SHELL, but takes precedence over SHELL.  It
> is designed for those cases where people have SHELL defined for other
> tools, and the value of SHELL is not good for Make.  (The description
> is in README.dos file inside the Make distribution, and also in the
> Info docs, under "Command Execution".)

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.

> > I have had some problems with makefiles using Bash that
> > worked without MAKESHELL but not with it.
> Please tell what were the problems, and how did you set MAKESHELL.

Oh, oh, don't remember... Never mind, as soon as I encounter the
problem it again, I'll ask again. I once set +MAKESHELL=bash under
[make] in djgpp.env (I know, I shouldn't edit it myself...).

-- 
Groeten, Michel.        http://www.cs.vu.nl/~mdruiter
  ____________
  \  /====\  /          "You know, Beavis, you need things that suck,
   \/      \/           to have things that are cool", Butt-Head.

- Raw text -