From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Tue, 22 Aug 2000 00:22:12 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Problems with depcomp from fileutils 4.0x & bash 2.03
Message-ID: <39A1C7B4.6304.3D3D4D@localhost>
In-reply-to: <200008220358.JAA01049@midpec.com>
References: <3099-Sun20Aug2000190425+0300-eliz AT is DOT elta DOT co DOT il>
X-mailer: Pegasus Mail for Win32 (v3.12c)
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

>> There's a huge difference between these two files. After trying the
> new files from Juan, I again got the same error. Surprisingly, it
> compiles under Windows.

Does Bash 2.04 produce a "good" config.status under Windows like 2.03?

I see that the configure script was produced with Autoconf 2.14a. Yuck. 
Unfortunately, Autoconf 2.14a isn't the best version of Autoconf for the 
maintainer to be using and this may make it more difficult to track down the 
problem. 2.14a is an alpha being an alpha has bugs. One of which is that 
2.14a uses the pattern '?:[\\/]*' to match DOS paths. Unfortunately, matching 
'[\\/]' is unreliable under Bash 2.03, but fixed with a patch from the Bash 
maintainer in 2.04.

Mark