Date:	Mon, 10 Apr 2000 08:36:28 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Prashant TR <tr AT midpec DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Porting problems with Sh-utils (beta)
In-Reply-To:	<200004091317.SAA00692@midpec.com>
Message-ID:	<Pine.SUN.3.91.1000410083609.19649B-100000@is>
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

On Sun, 9 Apr 2000, Prashant TR wrote:

> Ok, I have a simple makefile and a script here. Usually in both the sets of
> makefiles, the output "There is no bug in BASH!" is expected. However, the
> first case doesn't show it while the second does! I tried the same thing on
> Linux, but it works alright (shows the message both the times).
> 
> *****************************************
> Makefile:
> -----
> SHELL = /bin/sh
> 
> all:
> 	source='There is no bug in BASH!' \
> 	$(SHELL) ./script \
> 	echo `echo`script executed
> *****************************************
> 
> Script:
> -----
> #!/bin/sh
> 
> echo $source
> *******************************************
> 
> Makefile (version 2):
> ----
> SHELL = /bin/sh
> 
> all:
> 	source='There is no bug in BASH!' \
> 	$(SHELL) ./script \
> 	echo script executed
> *******************************************

Mark, can you comment on this?  I can confirm that, as long as there's
some `command` after "./script", the script gets an empty value for
$source.

- Raw text -