delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/12/16/13:57:39

X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112161859.AA21933@clio.rice.edu>
Subject: Re: The Bash 2.05 fixinc.sh bug
To: eliz AT is DOT elta DOT co DOT il
Date: Sun, 16 Dec 2001 12:59:16 -0600 (CST)
Cc: snowball3 AT bigfoot DOT com, djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au
In-Reply-To: <1858-Sun16Dec2001200955+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Dec 16, 2001 08:09:57 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> 
> > From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> > Date: Sun, 16 Dec 2001 09:51:23 -0600 (CST)
> > > > 
> > > > SHELL = /bin/sh
> > > > all:
> > > >         MAKE="$(MAKE)"
> > > 
> > > This probably means that the file it compains about is the temporary file 
> > > created in $TMPDIR, which is then submitted to Bash for execution.  What 
> > > is the exact error message printed when this Makefile is run?
> > 
> > This should just be a symbol substitution, ie make=make.
> 
> That's true, but how do you expect Make to know about that?  It
> doesn't; all it sees is a command line with some shell magic (the `='
> character), so it invokes Bash.  Shell invocation goes through
> `system', which, in the case of Unixy shells, does that via temporary
> files.  That's why I guessed that the problem is with the temporary
> file: after all, that's the only file that seems to be involved.
> 
> Of course, this is all pure theory; I didn't have a chance to step
> with a debugger into Make or the library and see if I remember this
> stuff correctly.

Let me clarify.  Using the exact same make.exe image, this works fine
with bash 2.04 built with the refresh.  With bash 2.05 it does not work.
That seems to indicate to me the problem is with bash 2.05 and has 
nothing to do with make.

All I did to change behavior was rename the various bash.exe images.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019