From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Thu, 18 May 2000 11:39:38 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: GDB 5.0 is in pretest
Message-ID: <3923D67A.15415.167179@localhost>
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10005170959210 DOT 27592-100000 AT ieva06 DOT lanet DOT lv>
In-reply-to: <Pine.SUN.3.91.1000518115927.12245W@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

On 18 May 2000, at 11:59, Eli Zaretskii wrote:

> 
> 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.

We only must get libtool to have reasonable value to avoid failures
when installing libraries. Therefore I think we should not relay on user
supplying correct value. Maybe even we should add test for bash version and require 
2.0.X or higher.

like 

case $BASH_VERSION in 1.*) echo Please use BASH 2.0.3 or above;exit 1 ;; esac;

Andris