Bug 173239 - kdevelop failed to compile source files
Summary: kdevelop failed to compile source files
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: 2008-10-21 15:45 UTC by wang feng
Modified: 2008-12-22 16:42 UTC (History)
2 users (show)

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 wang feng 2008-10-21 15:45:51 UTC
Version:           kdevelop 3.5.3  (using KDE 3.5.10)
Compiler:          g++ 4.3.2 Configured with: ../configure --prefix=/usr --enable-shared --enable-languages=c,c++,fortran,objc,obj-c++,treelang --enable-threads=posix --mandir=/usr/share/man --infodir=/usr/share/info --enable-__cxa_atexit --disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic
OS:                Linux
Installed from:    Gentoo Packages

1。open kdevelop (3.5.3)
2。 Project -> New Project -> C++ ->Simple Hello world program,  fill in the project name, then pressnext until finish
3。 Build -> Run automake & friends
4。Build -> Run Configure
5。Build -> Compile file
Problem comes out, the whole system goes slower suddenly, and I checked the 
ps aux
...
feng     17344  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17345  0.0  0.0  19260   740 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17346  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17349  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17350  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17351  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17354  0.0  0.0   9828   640 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17355  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17356  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17359  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17360  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17361  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17363  0.0  0.0   9828   640 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17365  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17366  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17369  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17370  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17371  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17374  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17375  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17376  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17379  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17380  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17381  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17382  0.0  0.0   9828   640 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17385  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17386  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17389  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17390  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17391  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17394  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17395  0.0  0.0  19260   736 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17396  0.0  0.0  19260  1548 ?        S    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17397  0.0  0.0   9828   640 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17400  0.0  0.0  19260   640 ?        R    22:38   0:00 /bin/sh ../libtool --no-reexec
feng     17401  0.0  0.0  19260  1544 ?        R    22:38   0:00 /bin/sh ../libtool
feng     17402  0.0  0.0   9828   644 ?        S    22:38   0:00 /bin/sed s%^.*/%%
feng     17403  0.0  0.0  19260   636 ?        R    22:38   0:00 /bin/sh ../libtool
feng     17404  0.0  0.0      0     0 ?        Z    22:38   0:00 [libtool] <defunct>

and more and more process keeps on generating.
Comment 1 Andreas Pakulat 2008-10-21 17:25:01 UTC
this is a problem in libtool, please report to the autotools people
Comment 2 Andres Chavarria 2008-12-22 14:26:50 UTC
I can confirm this bug for: 

OpenSuSE 11.1

kdevelop --version
Qt: 3.3.8b
KDE: 3.5.10 "release 21.11"
KDevelop: 3.5.3

gcc --version
gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


I found a way to avoid this. In the optimized or debug directory the libtool script contains the following definition for ECHO:

# An echo program that protects backslashes.
ECHO="printf %s\\n"

Changing the ECHO to lowercase solves the problem, i.e. change to:

# An echo program that protects backslashes.
echo="printf %s\\n"

I reported this to the libtool developers and these were astonished that "$echo" was being used. They are the opinion that the error is within KDevelop. I cite Ralf Wildenhues from the libtools developers:

Hello Andres,
 
* Andres Chavarria wrote on Sun, Dec 21, 2008 at 11:35:59PM CET:
> 
> > That's pretty weird. Libtool 2.2.x should not use $echo anywhere.
 
> And for grep '\$echo' ./libtool (it seems to use echo :))
 
Then it is using ltmain.sh from 1.5.x. Please report that bug to
whatever IDE you are using. They need to fix this.
 
Thanks,
Ralf


Greetings,

Andrés

Comment 3 Andreas Pakulat 2008-12-22 14:47:04 UTC
Well, then I suggest to use a libtool version that works with KDevelop projects, apparently libtool 2.2 doesn't work. The ltmain.sh thats mentioned here is from a shared directory, i.e. shared among all KDE 3.5 modules. Apparently someone should either adjust that ltmain.sh, or adjust the other autotools scripts in that directory to bail out if used with libtools 2.2. However KDE 3.5 development is largely dead and most probably there are few if any people able (as in understand that broken buildsystem) and willing to do these changes.
Comment 4 Andres Chavarria 2008-12-22 15:01:37 UTC
Thanks for answering.

If I understand correctly, either the user changes the scripts manually or the user waits until KDevelop 4.0 is released and offered as a package.

Good thing that it is so simple to correct the script manually.

Greetings,

Andrés

Comment 5 Andreas Pakulat 2008-12-22 16:42:51 UTC
Manually editing ltmain.sh is the only option in the mid-term future as KDevelop4 doesn't have any autotools support.