[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 92319] New: libtool targets have extensions problems
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: 2004-10-29 11:51:53
Message-ID: 20041029135153.92319.pierre.linux59 () wanadoo ! fr
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=92319
Summary: libtool targets have extensions problems
Product: kdevelop
Version: 3.1.1
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: pierre.linux59 wanadoo fr
Version: 3.1.1 (using KDE 3.3.1, SuSE)
Compiler: gcc version 3.3.3 (SuSE Linux)
OS: Linux (i686) release 2.6.4-52-default
Hi
I'm actually developing a project which uses :
- a lib : libfpkg
- a command-line interface to that lib : fpkg
For the interface itself, no problem. But I have got a big bug for libfpkg.
When I give libfpkg the name libfpkg, it installs itself in /usr/lib by creating the following files :
libfpkg -> libfpkg.0.0.0
libfpkg.0 -> libfpkg.0.0.0
libfpkg.0.0.0
libfpkg.a
libfpkg.la
Where is the .so extension ?
When I give it the name libfpkg.so, it installs the following files in /usr/lib :
libfpkg.so -> libfpkg.so.0.0.0
libfpkg.so.0 -> libfpkg.so.0.0.0
libfpkg.so.0.0.0
libfpkg.so.a
libfpkg.so.la
It's unusable too !
I didn't see any option to correct that problem... I think it's a serious bug of kdevelop...
I hope the informations I gave are enough to allow you to solve the problem...
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic