Hi all, ksplash-ml doesn't compile with the new autoconf-2.5.3a, that is used by the build process, even if I specify WANT_AUTOCONF_2.1. the build brakes, after successfull completion of automake with a call to autoheader, it compiled fine with previous versions (and kde-3.0.1 has no problem either) <output> cd . && autoheader configure.in:34: error: m4_popdef: undefined macro: AC_Dest ../autoconf/status.m4:831: AC_CONFIG_FILES is expanded from... configure.in:34: the top level autoheader-2.53a: autom4te failed with exit status: 1 at /usr/bin/autoheader-2.53a line 163 make: *** [stamp-h.in] Error 1 </output> As I submitted the ebuild, I'll dig into it, but really don't know how far I will come. Anyway, the best would be to mask it IMHO, regards, Tom
Tom, any news on this?
not really, it compiles fine if I run # autoheader # make in /var/tmp/portage/ksplash-ml-0.94.1/work/ksplashml-0.94.1 after the build brakes I don't undestand, how the sandbox works, for example: I don't understand the line ../autoconf/status.m4:831: AC_CONFIG_FILES is expanded from... ; relative to what is this path? I have not given up completely, but work demands a lot (just came home, it's 00.00 here :( ), so maybe leave the bug open for a while, I'll come back to it, not soon, but I will... Nice possibility to learn a bit about autoconf/make I guess regards, tom
Created attachment 1572 [details] ebuild script for new version with fixed autoXXXX handling ebuild script for new version with fixed autoXXXX handling, this is version 0.95.1; cooool :-) kind regards, tom
I just got this bug now. Can it be closed? We now have ksplash-ml-0.9.5.2 in portage, which seems to work ok (and doesn't need to run autoheader at all).
OK, AFAIK this is fixed, if not say so.