In kdevelop I started a new project. Added a file and then ran automake and friends. kdevelop doesn't realize that libtool has been updated and... More fallout from the dreaded sanity check. If there is a different version of the libtool and ltmain libtoolize isn't called for new projects. (Is this a bug for kdevelop?) *** Gentoo sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.10, ltmain.sh = 1.5) *** Reproducible: Always Steps to Reproduce: 1.emerge kdevelop 2.wait a few months for ltmain to upgrade to a new version 3.start a new project in kdevelop 4.kdevelop fails automake and friends with a gentoo sanity check.
This bug is related to (but not the same as) http://bugs.gentoo.org/show_bug.cgi?id=73140
It seems kdevelop devs are aware of the problem: http://www.kdevelop.org:8080/phorum5/read.php?2,25632,26598 http://bugs.kde.org/show_bug.cgi?id=92319 and we cannot do anything on the Gentoo side, a solution should come from them (or it is already fixed? it's not clear from the forum thread...) Anyway, I'm closing as UPSTREAM.
I think that's the best resolution this bug could have gotten. Thanks for taking the time.
Please reopen. I am getting the same issue with KDevelop 3.4: *** [Gentoo] sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.22, ltmain.sh = 1.5a) *** Please run: libtoolize --copy --force Running "libtoolize --copy --force" solves the problem but, still, kdevelop should be working out of the box.
*** Bug 231702 has been marked as a duplicate of this bug. ***
bug upstream: http://bugs.kde.org/show_bug.cgi?id=92319 seems like they are not into solving the bug no matter it is still present at least in my Gentoo install. Maybe I am not alone by the way.
