Date:	Sun, 9 Apr 2000 13:09:02 +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:	<200004091134.QAA00645@midpec.com>
Message-ID:	<Pine.SUN.3.91.1000409130448.9347B-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:

> Looks to me like a bug in BASH. To verify this, I did the foll:
> 
> 1> Copied out the lines manually to the bash shell and tried. No, it didn't
>    work.
> 2> Modified the last line to 
>          $(COMPILE) -c -o $@ $<
> 
>    and it works! In fact BASH doesn't like anything within the `....`

I find the last assertion hard to believe, at least in general.  `...` 
works for me in many cases, at least in Bash 2.03.  What version of Bash
do you use?

So please post the details, I'm sure Mark would like to see them.  If you 
can come up with a short Makefile to reproduce just this problem, please 
post it.  If not, post all the relevant files.

> Unfortunately, the diffs I sent to the Sh-utils maintainer during the previous
> beta release was lost because of change in his E-Mail ID. So, I'll have to send
> them to him again :-(.

I'd suggest to wait with the patches until we understand this weird 
problem.

- Raw text -