From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: What versions of bash should the next autoconf support?
Date: Sun, 18 Feb 2001 10:43:13 +0100
Message-ID: <CAEGKOHJKAAFPKOCLHDIOEKMCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Reply-To: djgpp-workers AT delorie DOT com

As the subject says - older versions of bash did not grok
files with mixed line endings.  I worked around this by
dtou'ing config.status.  However, this breaks when running
 config.status --recheck
as config.status is kept open by, so dtou can't move its
temp file over it (configure uses redirection to create
the new config.status, so that works).
So I added an ugly hack to work around this. So I wanted to
know if it was OK if autoconf didn't support any bash prior
to 2.03 (or any other shell that doesn't grok mixed EOLs).