[SOLVED] Claws-mail failing to build on slackware64-15.0
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.
Hello there, I'm new to slackware and I'm trying to building claws-mail from slackbuilds.
However, with any version (I've tried with older versions aswell), it fails to build.
I don't know exactly where to find the error or missing piece.
The build log is the following one:
Hello there, I'm new to slackware and I'm trying to building claws-mail from slackbuilds.
However, with any version (I've tried with older versions aswell), it fails to build.
I don't know exactly where to find the error or missing piece.
The build log is the following one:
If you are not working with a full install of Slackware and if you don't use J-Pilot, the perhaps adding "--disable-jpilot" to the ./configure options in the build will work, until you run in to another issue. If your lucky it will build to completion.
First of all, I would like to thank you all for your time and patience trying to help me. It's my first time in a Linux community (and in the Slackware community aswell), and this is the best start that I could ever ask. Furthermore, sorry for the late reply here.
@ponce
I have read that post before posting too, although it wasn't too helpful, as I could not find the proper answer. In fact, I did not make a complete full install of Slackware, but I just removed some specific packages (I did removed them in past installations too, without problems) that I don't think that there's a correlation with this problem: cdparanoia, cdrao, cdrtools, cdparanoia, and stuff like that; but probably this time I have removed something crucial too. I would just like to figure it out what is the missing piece that I could not find.
It wasn't possible to compile JPilot from SlackBuilds, exactly as the other post describes:
Code:
checking for GTK+ - version >= 2.0.3... yes (version 2.24.33)
checking for pilot-link header files... found at /usr/include
checking for pilot library files... found at /usr/lib64
checking for gethostent... yes
checking for setsockopt... yes
checking to see if I can compile a pilot link program... no
configure: error: Could not compile a test pilot-link program
And I could not figure it out the problem there too, even reading the Makefile/configure and having pilot-link installed.
@chrisretusn
Thanks for all the helpful answer, I have installed libetpan from SlackBuilds too, even though the error persists, but passing the flag --disable-jpilot to the --configure section of the claws-mail.Slackbuild solves the issue.
I think that this post can be marked as solved, exactly as the other post: the fault is mine with not doing a full install.
For everyone reading this in the future with the same problem:
you actually shouldn't need to install a separate jpilot as the error most probably originates from the internal jpilot of claws-mail: that jpilot is looking for some functions that are part of the pilot-link package that is provided with Slackware and that you choose not to install.
what I wanted to make you aware is that you most probably will have similar errors for other software that you will try to build from SlackBuilds.org and that will be specific to your custom installation: people that will make a full installation won't need to pass --disable-jpilot to the SlackBuild.
It wasn't possible to compile JPilot from SlackBuilds, exactly as the other post describes:
Code:
checking for GTK+ - version >= 2.0.3... yes (version 2.24.33)
checking for pilot-link header files... found at /usr/include
checking for pilot library files... found at /usr/lib64
checking for gethostent... yes
checking for setsockopt... yes
checking to see if I can compile a pilot link program... no
configure: error: Could not compile a test pilot-link program
And I could not figure it out the problem there too, even reading the Makefile/configure and having pilot-link installed.
@chrisretusn
Thanks for all the helpful answer, I have installed libetpan from SlackBuilds too, even though the error persists, but passing the flag --disable-jpilot to the --configure section of the claws-mail.Slackbuild solves the issue.
I think that this post can be marked as solved, exactly as the other post: the fault is mine with not doing a full install.
For everyone reading this in the future with the same problem:
Make a full Slackware installation
Pass --disable-jpilot to the Slackbuild
Glad the --disable-jpilot worked for you.
Hmm.. Okay I am guessing that you tried to build the SBo jpilot package to see if this would allow claws-mail to build. Did I guess right? Just curious. Thanks.
It's always best to use a full install of Slackware, especially if you are just starting out with Slackware. I've been using Slackware 31 years and I always do a full installation. Keeps things simple. Point in case, that jpilot most likely failed due to missing Slackware package(s). I don't use SBo, I create my own SlackBuilds. My claws-mail build has a number of configure options not included with the
SBo build. In addition to libetpan, I use bogofilter and webkit2gtk for the fancy plugin.
you actually shouldn't need to install a separate jpilot as the error most probably originates from the internal jpilot of claws-mail: that jpilot is looking for some functions that are part of the pilot-link package that is provided with Slackware and that you choose not to install.
what I wanted to make you aware is that you most probably will have similar errors for other software that you will try to build from SlackBuilds.org and that will be specific to your custom installation: people that will make a full installation won't need to pass --disable-jpilot to the SlackBuild.
Sure, sure, I got it, my fault, but I had the pilot-link package installed before trying to build claws-mail, so I don't think that this is the problem.
Quote:
Originally Posted by chrisretusn
Glad the --disable-jpilot worked for you.
Hmm.. Okay I am guessing that you tried to build the SBo jpilot package to see if this would allow claws-mail to build. Did I guess right? Just curious. Thanks.
It's always best to use a full install of Slackware, especially if you are just starting out with Slackware. I've been using Slackware 31 years and I always do a full installation. Keeps things simple. Point in case, that jpilot most likely failed due to missing Slackware package(s). I don't use SBo, I create my own SlackBuilds. My claws-mail build has a number of configure options not included with the
SBo build. In addition to libetpan, I use bogofilter and webkit2gtk for the fancy plugin.
I've been using Claws Mail for years. Love it.
Yup, I thought that this could help me find the correct answer, but didn't.
You're right about the full installation, I'm gonna start making things this way, I think it's better. Btw, claws-mail is an amazing software, really helpful.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.