vc/.lib

[W. Tasin]

Hi,

I don't think that this was a joke by Falk...
with your former explanation it is simply impossible to give a hint.

Often it is only because the user doesn't install kdevelop, but runs the 
binary from the source dir (so the libraries of the source dir are used).
Hint: "which kdevelop" or "whereis kdevelop".

Further... on my binaries (the installed version and the version inside 
the source-dir kdevelop/kdevelop/.libs/kdevelop) I really don't find a 
source path like you mentioned recorded inside the binaries.

What did the "make install" say after entering in kdevelop/vc/? Do you 
see sth. like:
-----
make[1]: Entering directory `/kde-build/CVS-KDE/kdevelop/kdevelop/vc'
/bin/sh ../../admin/mkinstalldirs /usr/local/lib
 /bin/sh ../../libtool --silent --mode=install /usr/bin/ginstall -c -p  
libkdevelopvc.la /usr/local/lib/libkdevelopvc.la
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
make[1]: Nothing to be done for `install-data-am'.
make[1]: Leaving directory `/kde-build/CVS-KDE/kdevelop/kdevelop/vc'
 -----
Or simply delete the
libkdevelopvc.*
libkdevelopkwrite.*
libkdevelopgfxview.*
libkdevelopdbg.*
libkdevelopkpp.*
libkdevelopsetup.*
libkdevelopqextmdi.*
in /usr/local/lib first and then reinstall kdevelop to see if there is a 
"make install" or "libtool" or simply access-rights problem.

Maybe it is a libtool problem which occurs only on OpenBSD... is there 
somebody out there having the same problems (maybe also on other 
distributions)?

Ciao

Walter

Gerardo Santana Gomez Garrido wrote:

>On Thu, May 30, 2002 at 02:38:41PM +0200, F at lk Brettschneider wrote:
>
>>Gerardo Santana Gomez Garrido wrote:
>>
>>>When compiling kdevelop 2.1.1 for KDE 3 in my OpenBSD 3.1 box I get no errors
>>>(well, I small one, but already patched), but when I try to run it it tries
>>>to load a shared library in vc/.lib/ while its libraries are installed in
>>>/usr/local/lib
>>>
>>>What's wrong?
>>>
>>What did you do?
>>
>
>Is this a joke? I would better apreciate a solution instead.
>
>I can see gcc linking with -rpath, but the paths recorded in the "kdevelop"
>binary are wrong.
>
>I can see these warnings too:
>
>libtool: install: warning: `./vc/libkdevelopvc.la' has not been installed in `/u
>sr/local/lib'
>libtool: install: warning: `./kwrite/libkdevelopkwrite.la' has not been installe
>d in `/usr/local/lib'
>libtool: install: warning: `./gfxview/libkdevelopgfxview.la' has not been instal
>led in `/usr/local/lib'
>libtool: install: warning: `./dbg/libkdevelopdbg.la' has not been installed in `
>/usr/local/lib'
>libtool: install: warning: `./kpp/libkdevelopkpp.la' has not been installed in `
>/usr/local/lib'
>libtool: install: warning: `./setup/libkdevelopsetup.la' has not been installed
>in `/usr/local/lib'
>libtool: install: warning: `./widgets/qextmdi/src/libkdevelopqextmdi.la' has not
> been installed in `/usr/local/lib'
>
>
>Any ideas?
>
>>Ciao
>>F at lk
>>
>>
>>
>>
>>-
>>to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
>>unsubscribe »your-email-address«
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20020531/06f22517/attachment.html>