Date:	Tue, 6 Mar 2001 10:58:28 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc:	DJGPP workers <djgpp-workers AT delorie DOT com>,
	Jim Meyering <meyering AT ascend DOT com>
Subject:	Re: Fetish.pm band-aid (Fileutils testsuite)
In-Reply-To:	<3AA3FDD6.130C773F@phekda.freeserve.co.uk>
Message-ID:	<Pine.SUN.3.91.1010306105723.7922J-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 Mon, 5 Mar 2001, Richard Dawe wrote:

> > It is quite common for Unix-born test suites to not bother setting
> > $SHELL, since the default shell is good enough.  But for this to work
> > on non-Posix platforms, $SHELL _must_ be set.
> 
> Well, the Makefiles have $SHELL set to /bin/sh, but that does not appear
> to be enough. When I tried with $SHELL set to /bin/sh.exe (which exists),
> I did not have the redirection problems.

This is expected: "/bin/sh" is only supported in Makefile's and in the
first line of a shell script.  For `system' to use the value of
$SHELL, it must point to an actual file name of the shell, including
its full path and the extension.

> To configure Fileutils 4.0 and have the test suite avoid the redirection
> problems, I used the following:
> 
>     CONFIG_SHELL=$DJDIR/bin/bash.exe ./configure --disable-nls
> 
> $CONFIG_SHELL needs to be set rather than $SHELL, because
> share/config.site overrides $SHELL.

I'd suggest a more local solution: have Fetish.pm detect it runs in
the DJGPP environment (e.g., by looking at $DJDIR) and if so, export
"SHELL=/dev/env/DJDIR/bin/bash.exe" into the environment.

- Raw text -