X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112151834.AA20878@clio.rice.edu>
Subject: Re: GCC build with 2.03 refresh OK (Win2K, WinXP) - Ready for ?
To: eliz AT is DOT elta DOT co DOT il
Date: Sat, 15 Dec 2001 12:34:36 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <2110-Sat15Dec2001183957+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Dec 15, 2001 06:39:57 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

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

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.