Date:	Thu, 18 May 2000 11:59:52 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp-workers AT delorie DOT com
Subject:	Re: GDB 5.0 is in pretest
In-Reply-To:	<Pine.A41.4.05.10005170959210.27592-100000@ieva06.lanet.lv>
Message-ID:	<Pine.SUN.3.91.1000518115927.12245W@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 Wed, 17 May 2000, Andris Pavenis wrote:

> CONFIG_SHELL=`echo 'echo $0' | bash.exe -`
> case ${CONFIG_SHELL} in *.exe) ;;
> 	*) CONFIG_SHELL=${CONFIG_SHELL}.exe;
> 	   test -f ${CONFIG_SHELL} || exit 1
>            ;;
> esac;
> 
> export CONFIG_SHELL 

Thanks!

I think the same could be achieved by forcing SHELL and CONFIG_SHELL
values be /dev/env/DJDIR/bin/sh.exe.  Right now, djconfig.sh only sets
them if they aren't already set.  This is so the script doesn't
override the settings that the user might have for some good reason,
but maybe it does more harm than it helps, in this case.

- Raw text -