Summary: | kdevelop failed to compile source files | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | wang feng <wanng.fenng> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | apaku, el_andrecillo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
wang feng
2008-10-21 15:45:51 UTC
this is a problem in libtool, please report to the autotools people 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 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. 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 Manually editing ltmain.sh is the only option in the mid-term future as KDevelop4 doesn't have any autotools support. |