X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Sun, 16 Dec 2001 08:41:01 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender:	pavenis AT ieva06
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc:	eliz AT is DOT elta DOT co DOT il, djgpp-workers AT delorie DOT com
Subject:	Re: GCC build with 2.03 refresh OK (Win2K, WinXP) - Ready for ?
In-Reply-To:	<10112151834.AA20878@clio.rice.edu>
Message-ID:	<Pine.A41.4.05.10112160833430.25478-100000@ieva06>
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 Sat, 15 Dec 2001, Charles Sandmann wrote:

> > > creation of fixinc.sh fails the same way under Win2K and WinXP, does not
> > > matter if I use make and other utils built with 2.03 refresh or Andrew's.
> > > Did not try to rebuild bash.  Manually created fixinc.sh and it 
> > > then continues (on both platforms).
> > 
> > Any ideas why would it fail?  I'd like at least to have some hint
> > befor we decide it's a non-issue.
> 
> "cannot execute binary file" only appears in bash.exe - so this seems to be
> a bash issue.  Since the build instructions talk about using bash 2.03,
> and Andrew has noticed numerous changed behavior between 2.04 and 2.05,
> I assume it's some change in bash (he did most of his work with 2.04).
> Since I didn't rebuild bash with the refresh, this is a cvs issue, or
> a bash issue, or some new issue instead of a refresh item.

I normally used bash-2.0.4 when it was out (or some beta versions from
Mark). Note in readme file means that one should have at least 2.0.3
as I had rather serious problems with old bash-1.4.17 (or which was the
version number ...). In last time I used last beta of bash-2.0.5 from Mark
to bootstrap gcc-3.1 CVS version under Win98SE. No tests done under 
Win2K/XP though. 

So don't count notice of bash-2.0.3 in readme.DJGPP too serious and don't
try more old versions. 

Also please make sure You have old needed stuff installed. Otherwise ove
can get strange error messages and it may be difficult to figure out
what really happens 

> 
> Since the machine I'm doing the builds on takes many hours (200Mhz class)
> I'd prefer not to spend my time chasing down issues like this.  The next
> thing to try would be bash 2.04.  Since a refreshed bash and refreshed
> (also from CVS?) 2.953 chain are on the worklist, maybe it gets identified
> there.  I just would prefer not to delay the refresh on this issue.
> 

Andris

- Raw text -