You are not logged in.
Hi All,
It builds but doesn't run. Error message:
error while loading shared libraries: libQtSql.so.4: cannot open shared object file: No such file or directory
Qt 4.8.2-1 and qt3 1:3.3.8b-1 are installed. Help please.
Thanks
Offline
Qt 4.8.2-2 is the latest version and owns that file.
$ ls |grep libQtSql.so
libQtSql.so
libQtSql.so.4
libQtSql.so.4.8
libQtSql.so.4.8.2(first 3 are symlinks)
If after upgrading it still gives the error, try rebuilding it.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
OK, I updated and I now have qt 4.8.2-2 installed. I uninstalled qorganizer and rebuilt it and I have the same error message. Now perhaps this is odd:
[a@Astudio ~]$ ls |grep libQtSql.so
[a@Astudio ~]$
I get nothing. Hopefully this is an easy one, thanks for the reply.
Offline
sorry, forgot to include the folder .
those are the files you should have if you run it in /usr/lib/
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks
[a@Astudio ~]$ cd /usr/lib/
[a@Astudio lib]$ ls |grep libQtSql.so
libQtSql.so
libQtSql.so.4
libQtSql.so.4.8
libQtSql.so.4.8.2
[a@Astudio lib]$
but still:
[a@Astudio ~]$ qorganizer
qorganizer: error while loading shared libraries: libQtSql.so.4: cannot open shared object file: No such file or directory
[a@Astudio ~]$
I don't have a very good grasp of this stuff but I noticed that there is no version for qt specified in the pkgbuild, or maybe it needs the path to libQtSql.so.4 specified?
Offline
it does look a bit weird that qmake and make have no parameters at all .
Please post the complete output of makepkg (use a pastebin site) , there may be warning messages that shed some light on this.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi Lone Wolf,
I really appreciate your responses but fixing stuff from AUR seems to be a bit over my head. First, I'm not sure how to get the output of makepkg and second, I don't know how to use a pastebin (I never even knew they existed). There are several pastebin clients listed here:
https://wiki.archlinux.org/index.php/Pastebin_Clients
If you can recommend a newbie friendly one I'll try to figure out how to use it.
Thanks
Offline
when run from a terminal makepkg sends all output while building a package to that terminal.
(some packages output 10k+ lines during building).
run something like this to get the output in a textfile :
makepkg >buildlog.txtFor using pastebins once in a while, you can use their webinterface and don't need a client.
goto pastebin.com (or another pastebin site) .
open the buildlog.txt file in any editor, copy/paste the contents to the pastebin page.
Choose the settings you feel are correct, click submit.
(i usually select paste expiration 1 month & paste exposure: private so it won't show up in searches/indexes and reduces traffic /load/storage on the pastebin server)
This stores the text you submitted on the pastebin server and you will be shown an url to access it.
Post the URL here and everyone who follows the link can see the content you pasted there.
You may want to bookmark the link, so you will be able to find it again.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks again! Here's the output:
Offline
oops, seems my memory tricked me.
when you set paste exposure to private, only you can see it.
please copy/paste it again, but this time with post exposure to public.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
OK, it's been fixed!
Offline
Ok, the build log doesn't give any clues about the problem, so decided to build the package myself and run namcap on the package.
On my x86_64 system, this is the output :
[panoramix@obelix qorganizer]$ namcap qorganizer-3.1-5-x86_64.pkg.tar.xz
qorganizer W: Referenced library 'libQtNetwork.so.4' is an uninstalled dependency
qorganizer W: Referenced library 'libQtSql.so.4' is an uninstalled dependency
qorganizer W: Referenced library 'libQtGui.so.4' is an uninstalled dependency
qorganizer W: Referenced library 'libQtCore.so.4' is an uninstalled dependency
qorganizer E: Dependency lib32-gcc-libs detected and not included (libraries ['usr/lib32/libgcc_s.so.1', 'usr/lib32/libstdc++.so.6'] needed in files ['usr/bin/qorganizer'])
qorganizer W: Dependency included and not needed ('qt')
[panoramix@obelix qorganizer]$Since the libQTxxx files do belong to Qt according to pacman -Qo , combined with the reference to lib32-gcc-libs does suggest qorganizer needs 32-bit libraries.
I installed lib32-qt (lib32-gcc-libs was already installed) , and ran namcap again.
[panoramix@obelix qorganizer]$ namcap qorganizer-3.1-5-x86_64.pkg.tar.xz
qorganizer E: Dependency lib32-qt detected and not included (libraries ['usr/lib32/libQtNetwork.so.4', 'usr/lib32/libQtCore.so.4', 'usr/lib32/libQtGui.so.4', 'usr/lib32/libQtSql.so.4'] needed in files ['usr/bin/qorganizer'])
[panoramix@obelix qorganizer]$ My conclusion is that the dependency for Qt in the packagebuild is wrong, and should be lib32-qt instead.
(it's likely that when the package was last updated lib32-qt was not a separate package).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
So I would just replace "qt" with "lib32-qt" in the pkgbuild?
Offline
So I would just replace "qt" with "lib32-qt" in the pkgbuild?
Yes, that is a necessary change for qorganizer to run .
Keep in mind though that the v1.3-5 version was released in august 2010, almost 2 years ago, so there may be other problems.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi Lone Wolf,
Yes, there are lots of other problems but thanks very much for your replies. I learned some things from you that I know will be useful in the future. Again, thanks for your time and patience!
Offline