It's not very important to support the latest autoconf since it isn't used when a source dist is compiled. It's more important that we (the developers) use whatever autoconf versions that suit us, and agree about it.
Besides, from what I've gathered things have been changing incompatibly between almost every minor release of autoconf lately. If that's correct then I don't think it's worthwhile to try to support it until it has settled again. Then we can port all the m4 code to it and simply drop support for 2.13.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-01-28 22:36: Subject: Re: OpenSSL wrapper vs Pike's SSL (Was: Bz2)
On Tue, Jan 28, 2003 at 10:10:05PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Most people get it to work though. Which kind of speaks against you doing things "more right than most people". :-)
"./configure; make install" supposed to work, right? That is what most people do. Now, since it doesn't in my case (on my system), it might (and eventually will) fail on other systems as well. Not on every, though, but anyway. The problem is that Pike (especially 7.4.10) isn't running or compiled on thousands of systems, otherwise my particular problem wouldn't be so particular :) BTW, why then 7.4.13 (assembled from CVS) was correctly compiled and SSL stuff _did_ work after "./configure; make"? :)
When I say "I can get it to work" it means that I can tweak the source, the configuration or whatever it is and to fix any problems, what most people won't (be able to) do.
In this particular case (SSL/Calendar) I don't need it _now_, so I didn't spend any time trying to figure out where is the problem. I just noticed that it doesn't work, that testsuite fails, that's all.
Also, I would like to mention that CVS version of Pike 7.4 is not really useable when latest version of autoconf is installed (I had to degrade it to very older version), but what the heck... Not everyone is even knows what CVS is, right? :)
Regards, /Al
/ Brevbäraren