SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In the past year there was a thread [1] where it was said that rtorrent could be used in Slackware Current.
Tried to install it on my Current x86_64, but libtorrent fails with:
Code:
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib/libcrypto.so when searching for -lcrypto
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib/libcrypto.a when searching for -lcrypto
/usr/lib64/../lib/libstdc++.so: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:515: recipe for target 'libtorrent.la' failed
make[3]: *** [libtorrent.la] Error 1
make[3]: Leaving directory '/tmp/SBo/libtorrent-0.13.6/src'
Makefile:562: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/libtorrent-0.13.6/src'
Makefile:494: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libtorrent-0.13.6'
Makefile:402: recipe for target 'all' failed
make: *** [all] Error 2
Both libtorrent (0.13.6) and rtorrent (0.9.6) versions that are mentioned in slackbuilds.org are the latest (http://rtorrent.net/downloads/).
Is there any patch for this? Or is there any other CLI torrent program slackware users are using that is similar or better than rtorrent?
that's strange, because libtorrent and rtorrent build fine here, on a standard slackware64-current: on a multilib slackware64-current you might have to modify the libtorrent.SlackBuild as indicated in the FAQ (untested here).
BTW, I'm personally using transmission from the command line.
/usr/lib64/../lib/libstdc++.so: error adding symbols: File in wrong format
As ponce indicated, it seems to be a multilib problem. Following the FAQ entry he linked will most likely solve your issue.
And, I'll second the use of transmission (although, I'm apparently not geeky enough to use it on the commandline and I prefer GUI frontends ). I haven't used rtorrent, but I'm a convert from ktorrent and have been plenty happy with transmission (and it works great with Android phones using Transdroid).
Just for extra info, transmission builds several different builds. I think there are 2-3 GUIs and one daemon. The clients are dual capable, in that they can run by themselves and provide all your torrent needs, or they can also double as clients where they just connect to another transmission server. For a long time, I was using one of the clients as the torrent program, but, eventually, I migrated to using transmission-daemon as my torrent server (since this can be run in the background without X and the others require a GUI to be started), then I can connect to that server using any number of clients, including the ones they provide and clients on other machines on my network (I have TransGUI on my Windows laptop that connects to the daemon on my server).
It was a little bit of a learning curve compared to other torrent clients I've used (Azureus way back in the day, then utorrent, the ktorrent, and finally transmission), but once I got it all figured out, I really think this is the best setup for my usage.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
). I haven't used rtorrent, but I'm a convert from ktorrent and have been plenty happy with transmission (and it works great with Android phones using Transdroid).
