delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Tue, 10 Apr 2001 13:35:56 -0400 |
MIME-Version: | 1.0 |
Subject: | RE: New bash 2.04 beta release |
Message-ID: | <3AD30C3C.9.75C575@localhost> |
In-reply-to: | <CAEGKOHJKAAFPKOCLHDIAEFACCAA.tim.van.holder@pandora.be> |
References: | <20010410112202 DOT C8356 AT kendall DOT sfbr DOT org> |
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 |
> The only thing that _would_ be REALLY useful is to have config.site > automagically adjust itself to the version of autoconf that was used to > generate the configure that's being run. First, thanks for working on it. I've noticed that 2.49e has PACKAGE_VERSION containing the version string which 2.13 doesn't have. That should be usable in distinguishing the two unless PACKAGE_VERSION is tossed in the future. And 2.49e uses PATH_SEPARATOR, so should the Bash config.site not set PATH_SEPARATOR=: as it does now? Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |