X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Sun, 16 Dec 2001 21:56:33 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Tim Van Holder" Message-Id: <3099-Sun16Dec2001215633+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: sandmann AT clio DOT rice DOT edu, snowball3 AT bigfoot DOT com, acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com In-reply-to: <000d01c18663$d41d9f80$d13276d5@pandora.be> (tim.van.holder@pandora.be) Subject: Re: The Bash 2.05 fixinc.sh bug References: <000d01c18663$d41d9f80$d13276d5 AT pandora DOT be> 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 Precedence: bulk > From: "Tim Van Holder" > Date: Sun, 16 Dec 2001 19:59:45 +0100 > > In fact, put 'MAKE="make"' in a file called 'foo', and 'bash foo' will > give the same error. Yes, because the key character here is the `='. Make knows that this character is special to a Unixy shell, so it invokes the shell when it sees `=' in the command. > Perhaps when invoking a Unixy shell through system, we should put > #! > as the first line, so that it is a real script? This was never required before. If Bash now requires that, I think it's a bug that should be fixed. Otherwise, people who use old ports of Make will not be able to use the new Bash. There's no reason for this incompatibility.