Date: Sun, 16 Jan 2000 10:16:46 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: "Mark E." cc: djgpp-workers AT delorie DOT com Subject: Re: Bash 2.03 prerelease now available In-Reply-To: <200001141850.NAA10705@delorie.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 14 Jan 2000, Mark E. wrote: > A release candidate version of Bash 2.03 is now available from: > http://snowball.frogspace.net/djgpp/ Thanks! One comment about the binary zip: Bash now comes with an Info manual, and we don't have an entry for it in info/DIR. So I suggest that readme.dos tells users to run install-info, to get their DIR file updated. (Too bad the pretest versions didn't come with the Info manual: if they did, I would've probably put the entry into DIR before releasing v2.03.) About the source zip: it failed to build for me (on Windows 98), complaining about parse errors and whatnot. It turned out that config.h was empty (it only has a single comment line produced by configure). I then wanted to configure it myself, but the readme doesn't tell what to do in this case (reconfiguring might be required if the distribution is compiled with a different version of library). I tried "sh ./configure" and it worked, but I think the docs should cover this. Does the ported distribution support building from another directory? If it does, I'll try that. If this isn't supported, I think the docs should say so. Btw, I understand that the configure script was produced by the DJGPP port of Autoconf. If so, that port needs more work, because the produced configure script still has some of the Unix-centric constructs that break on DOS/Windows. For example, the test for absolute name near ac_given_INSTALL doesn't support drive letters. (I can post a full list of problems, if someone is interested.) I also noticed that the build procedure invokes cmp, so Diffutils should be mentioned in the readme as a prerequisite. At least for reconfiguring, it will also need many other packages (Sed, Textutils, Sh-utils, and Grep, as the minimum).