Bug 102753 - Failed to build C++ Hallo World Template
Summary: Failed to build C++ Hallo World Template
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-29 17:16 UTC by Jakub Pastuszek
Modified: 2007-09-12 00:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Pastuszek 2005-03-29 17:16:52 UTC
Version:           3.2.0 (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r1, ssp-3.4.3.20050110-0, pie-8.7.7)
 
OS:                Linux

KDevelop failed to build C++ Hallo World template project.

When I started the building process I got:

...
/usr/share/aclocal/ORBit.m4:4: warning: underquoted definition of AM_PATH_ORBIT
installing -c
<And here message that he failed with status 1>

When I tried to ./configure it from terminal I've got this:

...
checking for correct ltmain.sh version... no

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.14, ltmain.sh = 1.5a) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

So I runned `libtoolize --copy --force` and after this everything was working fine.

I don't know if this is ebuild (gentoo) problem or kdevelop template problem but here is a link with information about it:

http://thread.gmane.org/gmane.linux.gentoo.devel/23449
Comment 1 Amilcar do Carmo Lucas 2005-03-29 18:01:47 UTC
There is really nothing that we can do about it.
We've added that to our FAQ. Thanks.
Comment 2 Markus Kreth 2006-07-28 21:45:56 UTC
The stable version 3.3.2 (and 3.3.3) has in the project templates-dir
(/usr/share/apps/kdevappwizard) wrong ltmain.sh versions (1.5a) but must be
1.5.22 .
Example: /usr/share/apps/kdevappwizard/template-common/incadmin.tar.gz.

This couses the need to execute "libtoolize --copy --force" in a projectfolder
every time a new project is created.

That is realy annoying  especially for devellopment rookies like me. Some days i start up to 4 projects.

I'd like to see something like copying the local /usr/share/libtool/itmain.sh into the templates during the install process.
Comment 3 Viktor Erdélyi 2007-09-11 23:07:23 UTC
Issue persists with Kdevelop 3.4.1. When will it be fixed, please?
Comment 4 Andreas Pakulat 2007-09-11 23:18:55 UTC
Well, it won't and can't be fixed as Markus suggests. At least not in a way that would work with packages. And we're barely working on KDevelop3 anyway.
Comment 5 Viktor Erdélyi 2007-09-11 23:37:33 UTC
Well the only problem is that there is a wrong "VERSION" setting in ltmain.sh. Can't you just query the libtool version and set that version as ltmain.sh version string? If I do it manually, it works... but for every single project, I have to do it myself.

B solution: put that libtoolize command somewhere between aclocal and automake or anywhere before configure. That should work too. However, I can't know how much work it involves and how much time you have for this.

Ps: you mean you'll be dscontinuing Kdevelop? Or you're working on Kdevelop4 and it'll be fixed in that version? What can I expect regarding the KDE software development stuff in the future?
Comment 6 Andreas Pakulat 2007-09-12 00:11:33 UTC
Putting a call to libtoolize after aclocal is not feasible because the boostrap Makefiles (called Makefile.cvs usually) are splattered all over the templates (nearly every template has a copy). Thats not correct, I know but too much work to change for too little gain it at this stage (sorry).

The version string also can't be changed because we fetch that from a central position in KDE's svn (branches/KDE/3.5/kde-common/admin). So I think you'd have the same problem when building kdevelop from svn or any other kde3 module for that matter.

About autotools support in KDevelop4: No idea how we will support that. There's some basic code already written, but nobody is currently actively working on it. Personally I don't care too much about autotools as its a broken buildsystem IMHO. However there's tons of other things planned and already implemented for KDev4, see the Wiki from our website for some developer-information and the blogs of us developers for some more information about user-visible changes. However Kdevelop4 is still pre-alpha, so don't expect too much at this stage.