X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs
Date: Mon, 2 Aug 1999 10:07:23 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Problems with gcc-2.95 and bash-1.14.7
In-Reply-To: <Pine.SUN.3.91.990801112022.20304H@is>
Message-ID: <Pine.A41.4.05.9908021003430.53762-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers 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, 1 Aug 1999, Eli Zaretskii wrote:

> 
> On Fri, 30 Jul 1999 pavenis AT lanet DOT lv wrote:
> 
> > build.bat calls 
> > 
> > 	redir -eo sh ./djbuild1.sh config >djconfig.log
> 
> Which version of redir did you use?  Is it from stock v2.02 or from
> the current CVS sources?  The one from v2.02 had a subtle bug in it.
> (Not that I'm sure this bug explains your problems, but still...)

It's from CVS source.

> 
> > Would it be acceptable to ask poeple to use bash-2.0.3 for building
> > gcc-2.95?
> 
> IMHO, it depends on the release schedules of GCC 2.95 and Bash 2.03.
> It's not reasonable to ask people to use Bash 2.03 if it is not yet
> released and available from SimTel.NET.
> 
> Perhaps if you could show what exactly fails and how, we could find a
> work-around.
> 

I found workaround by checking bash version:

	case ${BASH_VERSION} in 1.*)  ... ;;
			     in 2.*)  ... ;;
			     in *) echo "Wrong bash version"; exit 1; ;;
        esac;	

and adding code scpecific to bash version. So it should work now also with
bash-1.14.7

Andris