[SOLVED] Claws-Mail 3.11.1 fails to install on 14.1 multilib
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.
Claws-Mail 3.11.1 fails to install on 14.1 multilib
Since slackware doesn't have gtk-3-3.10 or gcr 3.10 and I can't install geary, I chose to go with claws-mail.
I isntalled clamav, gst1-plugins-base (installed earlier for another build), libwebp, webkitgtk, webkitgtk3 and gdata for the various plugins mentioned.
In reviewing the log for the installation -- libgdata is not found. So, it appears that gdata in slackbuilds is different than libgdata. Okay, possibly not an issue. Since I'm not failing out there, I'm just curious about this.
Hadn't really planned on installing jpilot, however I thought, well, maybe someone missed adding in jpilot as a requirement. Tried installing jpilot, that errored out because it couldn't complete the test pilot-link program. So, regardless of jpilot being required or not, jpilot doesn't install. I'm going to make the assumption that jpilot is REALLY NOT a dependency and there's a simple fix for this. However, reviewing the slackbuild, I can not figure out what it would be.
Should I simply email the maintainer, or has any one encountered this and how did they fix it?
Last edited by Anaximander; 02-18-2015 at 01:23 PM.
Hi, I have claws-mail 3.11.1 operating on my SLackware64 14.1 with multilib. I used SBOpkg, which is simply a frontend to Slackbuilds .org. i read the "REQUIRES" and included them. Everything worked and installed. However, I do not have clamav installed nor jpilot. Perhaps you should try the slackbuild first before trying to make your own package to see if the issue is claws-mail, your tools, or the plugin build. Best Regards, BrianA in MN
Hi, I have claws-mail 3.11.1 operating on my SLackware64 14.1 with multilib. I used SBOpkg, which is simply a frontend to Slackbuilds .org. i read the "REQUIRES" and included them. Everything worked and installed. However, I do not have clamav installed nor jpilot. Perhaps you should try the slackbuild first before trying to make your own package to see if the issue is claws-mail, your tools, or the plugin build. Best Regards, BrianA in MN
Do you have a full Slackware install? I was able to install claws-mail fine after installing the required libetpan program on my 14.1 system. If you do have a full Slackware install, it is possible that one of the plugins requires a dependency the slackbuild author didn't take into account. You could try temporarily removing some of the programs for those plugins and try recompiling.
I actually considered that last night and thought that I may have to do that. No, I didn't install XFCE (except those packages for thunar), or KDE.
I chose slackware because I could install only those things that I wanted. Regardless of the fact that I don't HAVE to use KDE, I'm hoping that I don't have to have it fully installed in order to install claws-mail. I think it may be best to email the maintainer and find out which packages I need to make sure I have installed for it to work.
Just so you're aware, a full install is recommended with Slackware; and any slackbuilds on slackbuilds.org assume that you have a full install. In actuality, the only reason to not do a full install is if you're limited on diskspace. Having KDE installed will not use up any resources other than diskspace unless you actually choose to run kde as your desktop or start any kde apps. But when you're trying to resolve dependencies, it is a lot easier to start with a full install, because then any slackbuild on slackbuilds.org will show the only required dependecies (and optional, as you saw) to compile that software. It takes out all the guesswork of dependency resolution.
But if you are worried about diskspace, you can try and check in the jpilot.c file and see what headers it includes. Then you can check the MANIFEST.bz2 file to find what packages includes those headers and see if it's installed (or use http://packages.slackware.com, but it can be slow). Hopefully this can help you find the missing dependency. But in googling your undefined references, it's looking to be something dealing with KDE (like kdepim) and it looks to do with the contacts portion of claws-mail. You can check in the ./configure --help to see if there's any way to disable it, but I don't know what the "it" is that you'd need to disable.
Just so you're aware, a full install is recommended with Slackware; and any slackbuilds on slackbuilds.org assume that you have a full install. In actuality, the only reason to not do a full install is if you're limited on diskspace. Having KDE installed will not use up any resources other than diskspace unless you actually choose to run kde as your desktop or start any kde apps. But when you're trying to resolve dependencies, it is a lot easier to start with a full install, because then any slackbuild on slackbuilds.org will show the only required dependecies (and optional, as you saw) to compile that software. It takes out all the guesswork of dependency resolution.
Yeah -- I know. I'm just a stubborn twaddle knob sometimes. I have a feeling that in the next few months I'll be getting new equipment and doing an LFS slackware install. I think until I get better at the basics, though, my best approach is just go the full monty. I'll have a full working system that I can look stuff up with and can take my time and get more in depth with linux when I go for the lfs route.
Quote:
Originally Posted by bassmadrigal
But in googling your undefined references, it's looking to be something dealing with KDE (like kdepim) and it looks to do with the contacts portion of claws-mail.
I'm all kinds of impressed on that, because I couldn't find the reference to kdepim. From what it sounds like I should have probably reduced the search words and just done the actual files -- and probably with out claws-mail what so ever.
And pataphysician, thank you for that pointer. Along with bassmadrigal, and everyone else, I'm just a bit better. I'm going to mark this solved. A) Good information pointing to a solution to the current technical problem. B) Sounds like I'd be better served for the moment, putting the rest in place.
Last edited by Anaximander; 02-19-2015 at 04:03 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
