Hello, You're receiving this canned (template-based) bug report because I found a problem with a package during my tinderbox run. The package in question is running automake (and most likely other autotools) during compile phase by maintainer-mode. You can see in my blog post in the URL field why that's a problem, and how to address the issue, but in general, you don't want maintainer-mode rebuild during compile phase, especially since it can cause multiple run of econf. The causes of maintainer-mode rebuild are various, but most likely it's because of a patch that changes Makefile.am or configure.ac/in and don't rebuild autotools properly. The way to fix this is almost always to inherit autotools eclass and run eautomake/eautoreconf (as needed; eautoconf should only be used when automake is not involved, which is not the case here) during src_unpack phase. Thanks, Diego
Created attachment 179258 [details] Build log
Unfortunately it's not entirely maintainer-mode, but the Makefile's call a cvs.sh and others in admin/ directory this package ships, as do many others KDE 3.x pkgs. Just adding eautoreconf won't make this problem go away, the build system would require some rewriting.. :-(
If it's using the kde3 build cr^Wsystem you should just remove the configure file and let kde.eclass handle it.
(In reply to comment #3) > If it's using the kde3 build cr^Wsystem you should just remove the configure > file and let kde.eclass handle it. > Thanks, that helped. :-) Still ugly, but doesn't rerun the stuff anymore.
