Summary: | Unable to "autoconf & automake", autoconf version conflicts? | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Antonio Su <asuarez> |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.1.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Antonio Su
2003-12-24 01:07:54 UTC
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 |