Problem compiling centerim, needs curl with ssl support
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.
AFAIK it's due to that curl itself no longer ships with certificates.
it's that the certs aren't there (Slack non-modified the upstream curl)
Perhaps a guru will step in and supplement and/or condense/reduce what I've offered here if necessary.
Probably not many people have need for it (for 1). And, 2, the old certs were outdated is one reason that the curl people stopped including certs as bundled with curl.
i forget now just how I got mine working. But I think I used a Perl script I downloaded from somewhere to create recent certs. And i think i recall using the slackware slackbuild and source for curl and built my own curl package, whereby I added/used an additional and relevent option to do with this, added said option into the slackbuild.
I Didn't know of the next when I got mine working but now I'm aware of the next.
there's more than one way to do this. here's a part of how I once did it (rebuilt curl **with pointer pointing to where my certs are) [those, the certs that *I* had created]. But beware, there may possibly be an easier way (than building curl *with* pointer to certs.).
curl 7_19_4 on Slack 12.2
next from my where I added a one liner into the build script
Code:
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--mandir=/usr/man \
--with-ca-bundle=/etc/ssl/certs/ca-certificates.crt \
^^^ added in that ^^ line at right there
Yes I'd found it there. And also on the curl site there used to be several choices, 1 of which was to make your own certs using a Perl script.
o.p. I just recalled some more: can make use of a command line switch when calling curl -- said switch in curl command in this case is the one that tells curl where the certs are. (no need to re build curl).
But I wasn't advanced enough at C programming to find where curl is called in the
that I was using so I could change in its source code where it calls curl.
So, in my case, it was easier for me to rebuild curl to be with its own pointer to my certs.
What's *not* clear to me is if there exists a default within curl as far as a search path and/or a naming convention for the certs <- thus, that if I got the path and naming convention correct for my certs then curl would just find the certs (without rebuilding curl).
I tried those sites first, and posted my question after realizing they were not useful for what I am asking.
Next time, try to actually say something rather than providing redundant links.
Wow, way to be aggressive.
Let's step through this, mmk?
Quote:
Originally Posted by Josh000
Actually, I am having problems with libraries for a few other applications as well.
<cut>
How would I find these libraries for Slackware, and tell if there is a slackware package availabe or not?
You ^find these libraries for Slackware^ via http://slackbuilds.org. A package will be available when you build one using the SlackBuilds which takes very little time.
The time is further reduced with the use of sbopkg which will build AND install them for you in any order you desire.
Anything that's already *in* Slackware can be found with a simple "slackpkg info" command.
$ slackpkg info qt
PACKAGE NAME: qt-r1008952-i486-1.txz
PACKAGE LOCATION: ./slackware/l
PACKAGE SIZE (compressed): 41172 K
PACKAGE SIZE (uncompressed): 102480 K
PACKAGE DESCRIPTION:
qt: Qt (a multi-platform C++ graphical user interface toolkit)
qt:
qt: Qt is a complete and well-developed object-oriented framework for
qt: developing graphical user interface (GUI) applications using C++.
qt:
$ slackpkg info libgcrypt
PACKAGE NAME: libgcrypt-1.4.4-i486-1.txz
PACKAGE LOCATION: ./slackware/n
PACKAGE SIZE (compressed): 396 K
PACKAGE SIZE (uncompressed): 1520 K
PACKAGE DESCRIPTION:
libgcrypt: libgcrypt (General purpose crypto library)
libgcrypt:
libgcrypt: Libgcrypt is a general purpose crypto library based on the code
libgcrypt: used in GnuPG.
libgcrypt:
I got centerim working by adding disable-yahoo as a configure option, which may be useful for others.
The SlackBuild for CenterIM on SlackBuilds.Org by nyRednek seems to work fine as it is for me on Slackware64-13.0.
As built by sbopkg:
Code:
+++++++++++++++++++++++++++++++++++++++++++
PACKAGE BUILDING/INSTALLATION SUMMARY LOG
Using the SBo repository for Slackware 13.0
Queue Process: Build only
centerim:
MD5SUM check for centerim-4.22.8.tar.gz ... OK
Building package centerim-4.22.8-x86_64-1_SBo.tgz ... OK
+++++++++++++++++++++++++++++++++++++++++++
Nonetheless, thank you for posting the solution to your problem so that others may find it.
Quote:
Originally Posted by Josh000
Also, I did not mean to be agresive, so I am sorry for that.
I downloaded the slackbuild and source again to replicate the error so I could post the config.log, and now it works fine. Without having to --disable-yahoo
I installed 4 extra packages in total, libsigc++, libnet, pygobject and python-dbus, the last 2 from the slackware dvd.
centerim uses none of these packages, so I am surprised and confused as to why this is now working. I would really like to work out how this is possible :S
edit: I wonder if this would have anything to do with logging out and then in again, but as it was checking for files I should think not...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.