Re: [GD-DEVEL] Call for test: 2.0.36
[email protected] ("Pierre Joye") Mon, 10 Mar 2008 13:40:27 +0100
| Newsgroups | php.gd.devel |
|---|---|
| Message-ID | <[email protected]> |
HI! On Mon, Mar 10, 2008 at 12:45 PM, Christian Schneider <[email protected]> wrote: > Pierre Joye wrote: > > Yes, that's the whole idea of the autotool script. I tested the > > package on a system without any autotools installed and it works. I'm > > not sure why FC7 + autoconf 2.59 raises this error. > > > > Does anyone else tested the package and had similar issues or get it > > compiled smoothly? > > Same problem here, it tries to run autoconf (which it shouldn't) and fails: > > cd . && /bin/sh /home/cschneid/src/gd-2.0.36/config/missing --run autoheader > > aclocal.m4:17: error: this file was generated for autoconf 2.61. > You have another version of autoconf. If you want to use that, > you should regenerate the build system entirely. > aclocal.m4:17: the top level > autom4te: /usr/bin/m4 failed with exit status: 63 > autoheader: /usr/bin/autom4te failed with exit status: 63 > > make: *** [config.hin] Error 1 > > BTW: I'd append some sort of identifier to the tar.gz (like RC1, RC2, > ...) so we can see when you are making changes and we should retest. I agree but this is not a release per se. I don't have many ways to get feedbacks right before an official release (to test/valid the final package). It is also why I put in my personal directory and not in libgd.org/releases/ . There was no change since RC1 and was supposed to be used directly as release if no problem was found (dream++). The goal was to avoid the problem we are trying to solve right now (it happened in 2.0.35 already). If there is a better way to do that, I will be happy to use it :) I was trying to escape the auto* pain as long as possible and failed miserably ;). I sat down this morning to read the source and the autotools manuals and finally update GD_2_0 autoscript files. They were missing the complete tests data, the platform specific directories like windows, netware, VMS as well as the CMakeLists.txt files. The tests suite can't be run via auto* (and I have no plan to do it as it uses ctest) but at least I can now create the release archive using the configure script, it should help to avoid our current problem. I did not test a full configure+make+make install now but the new files and the updated scripts are in CVS, branch GD_2_0 (cvs co -r GD_2_0 ...). I will finish the update later tonight. Please check it to see if I made some horrible changes or stupid mistakes. I also figured out what I did wrong in my last attempt last year, I have to define each single directory in configure.ac using AC_CONFIG_FILES :) Patch (or direct commit if you already have cvs access) are more than welcome. I hope we can fix this auto* mess once and for all. The bad news is that we will need a RC2. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org