Bug 59939

Summary: dependency_libs contains source paths and libs from gcc
Product: [Applications] kdevelop Reporter: Markus Mertens <mertema>
Component: generalAssignee: 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
Version:           2.1.5 (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc-3.2.3 
OS:          Solaris

Hi!

When I'm creating a shared library with kdevelop a file *.la is generated. This file contains a section "dependency_libs" in which all source and library paths from the used gcc are listed (see below). Even local paths from LDFLAGS are added. 

The most urgent problem is that I have to edit all *.la files (i.e. deleting all gcc paths) of all shared libraries ever created with kdevelop after a compiler upgrade. I'm wondering why they are added anyhow, because without them everything works fine (dependency_libs=' -m -lgcc_s').

Kind regards,

    Markus


-------------------------------------------
# Libraries that this one depends upon.
dependency_libs=' -L/usr/local/lib -L/opt/sfw/lib -L/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2.3 -L/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2.3/../../../../sparc-sun-solaris2.8/lib -L/usr/ccs/bin -L/usr/ccs/lib -L/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2.3/../../.. /usr/local/lib/libstdc++.la -L/usr2/SOURCES/S8/gcc-3.2.3/objdir/sparc-sun-solaris2.8/libstdc++-v3/src -L/usr2/SOURCES/S8/gcc-3.2.3/objdir/sparc-sun-solaris2.8/libstdc++-v3/src/.libs -L/usr2/SOURCES/S8/gcc-3.2.3/objdir/gcc -L/usr/local/sparc-sun-solaris2.8/bin -L/usr/local/sparc-sun-solaris2.8/lib -lm -lgcc_s'
Comment 1 Amilcar do Carmo Lucas 2003-06-17 13:48:00 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. 
 
Comment 2 Thiago Macieira 2003-06-17 14:09:52 UTC
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.