Version: 2.1.5 (using KDE KDE 3.1.4) Installed from: SuSE RPMsSuSE Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-144-default I have a KDevelop C++ project that used to build fine on KDevelop 2.1 (running on KDE 3.0.5 shipped with SuSE 8.0). I've moved the project to a box running SuSE 9.0 and found that the project can't be built, "Autoconf & automake" stops at this point: *** Creating configure configure.in:102: error: m4_popdef: undefined macro: AC_Dest /usr/src/packages/BUILD/autoconf-2.57/lib/autoconf/status.m4:844: AC_CONFIG_FILES is expanded from... configure.in:102: the top level autom4te: /usr/bin/m4 failed with exit status: 1 (Don't know if it's relevant, but there is nothing under /usr/src/packages/BUILD/ at this box. Anyway, softlinking the path above to /usr/share/autoconf/autoconf/ seems useless, same error.) I've tried some workarounds for these issue, as found around the Internet, with no results. One of them consists in downgrading to autoconf 2.52 or 2.53, but then running "Autoconf & automake" stops at: *** Creating configure ./aclocal.m4:10181: error: Autoconf version 2.54 or higher is required for this script ./aclocal.m4:10181: the top level I've also tried 2.54, and them the build fails in the same way that 2.57. Except for that: nice product. Thank you, guys.
I've managed to complete the autoconf pass with a dirty trick. I understand this is not the way to go and I'm not proud about it, but I'd like to set it down here so maybe it helps in solving this issue.I noticed that autoconf 2.52 would be nice if this line:AC_PREREQ([2.54])in aclocal.m4 wouldn't stop it from running. As aclocal.m4 is generated on the fly and I can't make persistent changes to it, I've modified the sources of autoconf 2.52 so it claims to be version 2.57. This way, the "Autoconf & automake" pass ends with no errors.Thank you again.
Sorry, KDevelop 2.x is no longer under development. You are strongly advised to update to the latest CVS version of KDevelop3, take a look at: http://www.kdevelop.org/index.html?filename=branches_compiling.html for all the details you need. If you find a problem or need help please send a mail to the mailing list: http://www.kdevelop.org/index.html?filename=mailinglist.html or drop us a line at the channel #kdevelop on the server irc.kde.org using ksirc, for example. Please use the CVS version and compile it yourself because that way you can easily patch it if a bug is found. KDevelop3 can open Develop2 projects. To do so, goto the "Project -> Open Project ... " and select "KDevelop 2 Project Files" in the "Filter:". So migrating is a breeze. :) P.S. : The KDevelop team closed over 80% of the reported and confirmed KDevelop 2.x bugs in KDevelop 3.0