Date: Sun, 18 Mar 2001 16:11:37 +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 AT delorie DOT com, Jim Meyering <meyering AT ascend DOT com>
Subject: Re: Fetish.pm band-aid (Fileutils testsuite)
In-Reply-To: <3AB4B541.2E8B3692@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1010318160853.13251B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sun, 18 Mar 2001, Richard Dawe wrote:

> > 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.
> 
> Well, I've hit another problem. It appears that the port of Perl 5.005_02
> has not been compiled with DJGPP 2.03, so it does not understand
> /dev/env/DJDIR.

You could then use $DJDIR/bin/bash.exe instead.  Perl should be able to 
access the environment variables, and $DJDIR should be in its 
environment.

In other words, once Perl runs on a specific system, it's okay to use 
the value of $DJDIR explicitly, because it's no longer a generic name.

> + # (richdawe AT bigfoot DOT com): If we're running in a DJGPP environment, set
> up
> + # $ENV{'SHELL'} to point to bash. If we don't do this, a bad shell might
> + # be used (e.g. command.com) and the tests will just fail.
> + if (defined($ENV{'DJDIR'})) {
> +     $ENV{'SHELL'} = $ENV{'DJDIR'}.'/bin/bash.exe';
> + }
> +

Looks like exactly what the doctor ordered ;-)