Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9815 - [krusader 1.80.0-1] doesn't start or compile

Attached to Project: Arch Linux
Opened by G_Syme (G_Syme) - Tuesday, 11 March 2008, 15:10 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 11 March 2008, 21:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After installing krusader from [extra], it doesn't want to start, and returns:

krusader: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory

But the file it complains about is present: /opt/qt/lib/libqt-mt.so.3

The source also doesn't want to compile, with a similar error. I've also removed kdebindings before compilation which was suggested in the PKGBUILD, and have changed the entry /etc/profile.d/qt.sh to /etc/profile.d/qt3.sh in the PKGBUILD because the other one isn't present (maybe because of the switch from qt3 to qt4), but nothing has helped.

Additional info:
makepkg-krusader.log: the output of makepkg, with the setup described above(removed kdebindings, changed /etc/profile.d/qt.sh to /etc/profile.d/qt3.sh in PKGBUILD).
Strange is that the output of configure says it has found the correct path for the qt-libraries:
qt_libraries: /opt/qt/lib

Steps to reproduce:
already described above.
   makepkg-krusader.log (39.6 KiB)
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Tuesday, 11 March 2008, 21:31 GMT
Reason for closing:  Not a bug
Comment by Igor (cheer) - Tuesday, 11 March 2008, 19:42 GMT
compiling from source works for me without changing PKGBUILD, it seems that is something wrong with your qt settings, because krusader works on my machine. Is your system up-to-date? What version of qt3 do you use?
Comment by G_Syme (G_Syme) - Tuesday, 11 March 2008, 20:08 GMT
My system is up-to-date. Installed versions of qt are:
qt 4.3.3-4
qt3 3.3.8-6.1
There are also no .pacsave ore .pacnew files which are associated with qt or kde.
I've also taken a look into /var/log/pacman.log but have found no note except that qt4 has been moved to /usr.
But that shouldn't be of concern because AFAIK krusader builds against qt3 and not qt(4).
Comment by G_Syme (G_Syme) - Tuesday, 11 March 2008, 21:12 GMT
I've solved the problem.
After being encouraged that I seemed to be the only one having this problem, I've searched the forums once again and have found the solution here:
http://bbs.archlinux.org/viewtopic.php?pid=231175#p231175
After the upgrade of the filesystem package, I had merged my old /etc/ld.so.conf with the new one and had all entries in it deleted because /etc/ld.so.conf.pacnew comes as an empty file. But to my surprise, even in my original /etc/ld.so.conf there was no "/opt/qt/lib" present, although I had qt and qt3 installed before, which should have inserted that entry into /etc/ld.so.conf according to the install scripts...
I've also found the following entry in the forums, which is pretty recent:
http://bbs.archlinux.org/viewtopic.php?id=45219
So maybe I'm not the only one who has that problem with qt...
But thanks anyway, and sorry for bothering.

Loading...