Summary: | dependency_libs contains source paths and libs from gcc | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Markus Mertens <mertema> |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.1.5 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Solaris | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Markus Mertens
2003-06-17 13:10:52 UTC
KDevelop 2.x is no longer under development. You are strongly advised to update to the latest CVS version of KDevelop3 code name gideon, 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 you you can easily patch it if a bug is found. KDevelop3 can import KDevelop2 projects. You can have and run KDevelop3 and KDevelop2 at the same time on the same computer without any problems. So migrating is a breeze. :) Besides that, this seams to be a libtool bug. Closing. Feel free to reopen if the bug presists in kdevelop3. It will persist and please do not reopen. That's how libtool works, so it's not a KDE bug and it's not even a bug. If you want it to change, please send the libtool maintainers a report. Another simpler solution is to simply re-run your configure script after a compiler upgrade. |