> I have been working with kde4 devel env since 2005 and i never use the kde4
> libraries path loaded by ldconfig, but using
> LD_LIBRARY_PATH=/usr/local/qt4/lib:/usr/local/kde4/lib:/usr/local/kde4/lib/kde4
I don't know what cmake does these days, but when I last experimented
with KDE4 in Augus
El Saturday 16 June 2007 8:16:13 am escribió:
> I seem to get exactly the same problems on my recently built KDE4
> system. Here is some example ldd output on the kfmclient residing
> inside my devel's user home directory:
>
> /home/devel/kde/bin/kfmclient:
> libkdeinit4_kfmclient.so =>
>
On Sat, Jun 16, 2007 at 12:39:50PM +0100, Bartosz Fabianowski wrote:
> I hit a very similar problem last August when first trying to compile
> KDE4 on FreeBSD. I added lots of debug outputs and found out that the
> problem was as follows:
>
> * Some Qt3/KDE 3 libraries have the same names and ve
I hit a very similar problem last August when first trying to compile
KDE4 on FreeBSD. I added lots of debug outputs and found out that the
problem was as follows:
* Some Qt3/KDE 3 libraries have the same names and version numbers as
their Qt4/KDE4 counterparts
* /usr/local/lib, where Qt3 and
Hi Guys
For more than 5 weeks there was introduced some bug on trunk, that makes
kio_file and other plugins fails when loaded.
example:
Could not open library '/usr/local/kde4/lib/kde4/kio_file.so'.
QLibrary::load_sys: Cannot load /usr/local/kde4/lib/kde4/kio_file.so (Cannot
open "/usr/local/k
