[SOLVED] Compiling from source

khinch · 10-14-2010, 12:29 PM

I recently started using Slackware 13.1 (defected from OpenSuSE 11.0) and I am trying to get to grips with software install. I use slackpkg to keep my core files etc up to date, and I have been trying to use slackbuilds.org to install other stuff like Digikam.

One of the dependencies of Digikam is provided by kipi-plugins, which is also available on slackbuilds, so I tried to install it via the script as per the instructions, but it fails to compile due to missing dependencies:
libopencv, libkdcraw and libkexiv2.

OpenCV is also available via slackbuilds, so I downloaded it, followed the instructions and it installed fine. But, now when I run the kipi-plugins script, OpenCV is still on the list of missing dependencies. Can anyone tell me what I am missing please?

Output from the build script:

Code:

--  kipi-plugins 1.4.0 dependencies results   <http://www.kipi-plugins.org>
-- 
--  libjpeg library found.................... YES
--  libtiff library found.................... YES
--  libpng library found..................... YES
--  libkipi library found.................... YES
--  libkexiv2 library found.................. YES
--  libkdcraw library found.................. YES
--  libxml2 library found.................... YES (optional)
--  libxslt library found.................... YES (optional)
--  libexpat library found................... YES (optional)
--  native threads support library found..... YES (optional)
--  libopengl library found.................. YES (optional)
--  Qt4 OpenGL module found.................. YES
--  libopencv library found.................. NO  (optional)
--  libgpod library found.................... YES (optional)
--  Gdk library found........................ YES (optional)
--  libkdepim library found.................. YES (optional)
--  qca2 library found....................... YES (optional)
--  libkdcraw >= 1.1.0 library found......... NO  (optional)
--  libkexiv2 >= 1.1.0 library found......... NO  (optional)
--  OpenMP library found..................... YES (optional)
--  libX11 library found..................... YES (optional)
--  libksane library found................... YES (optional)
-- 
CMake Error at CMakeLists.txt:247 (MESSAGE):
   kipi-plugins will not be compiled! Look README file for more details about dependencies...


-- Configuring incomplete, errors occurred!

Any help much appreciated.

johneb47 · 10-14-2010, 05:24 PM

Hi Khinch,
Having used the Slackware distro for many years I have found from experience to have all the Gnome and KDE libraries installed. This helps to reduce the dependency issue. YES as it says in your error message look at your README file/s and make sure you have all dependencies installed. This is always a requirement for the user who wants to compile their own software. Slackware doesn't believe in hand holding and expects the user to be able to resolve his own problems. It also doesn't believe in patching the software packaged by the development team. This put the onus of using, compiling and patching software squarely on the user's shoulders. It is for these reasons that I wouldn't recommend any inexperienced user to embrace Slackware unless he is prepared to put in the hard yards and READ READ READ and understand all the books, man pages and Linux Docs and guides available on the internet. From experience a fresh install of Slackware can take at least two to three months; 90% of the software is installed and configured inside a few hours the other 10% can take the two to three months. Although I have found it follows the natural log law and you are never completely satisfied and are always looking for some new developement to improve your system.

If the system doesn't recognised newly installed libraries try running 'ldconfig' as root.

I have found that Archlinux is a viable alternative to Slackware without any of the dependency issues. It also has the added advantage of having a rolling update ability that allows you to run the update script on a weekly/monthly/yearly cycle to keep your system completely up to date.

Regards

John

BrZ · 10-14-2010, 05:45 PM

KDE is shipping both now...

KDESC 4.5.2

/usr/include/libkdcraw/version.h

Quote:

static const char kdcraw_version[] = "1.1.0";

/usr/include/libkexiv2/version.h

Quote:

static const char kexiv2_version[] = "1.1.0";

khinch · 10-15-2010, 04:16 AM

Thanks for the replies.

BrZ: It's nice to know these dependencies are catered for in later versions of KDE. I am running version 4.4.3 and I think installing 4.5 is a little beyond my abilities right now though. Perhaps this is where my problem lies if I am trying to install a version which is written for KDE 4.5 when I am running 4.4.3?

johneb47: I have been doing a lot of reading recently; forum trawling, googling etc but I only posted here because I am stuck for answers to this particular question. Thanks for the idea about installing all of the libraries, that sounds like a good plan. Is there a way to install all of the KDE libs in one go or is it a manual process of hunting them all down and installing one at a time? I also have the same issue with ffmpeg - it fails to install saying "libmp3lame not found", even though I installed lame from here: http://slackbuilds.org/result/?search=lame&sv=13.1. I tried running ldconfig as you suggested but it didn't make any difference.

So, I suppose my question is; when I know a program has a dependency, how do I go about satisfying that dependency? I must be doing something wrong if nobody else is having the same problem.

Edit:
*FACEPALM*
I just realised that the slackbuild scripts don't actually install the files and they only make them. Once I manually installed the output files it worked fine. I would still be interested to know the best way of installing all of the KDE libraries though, if anyone has the time.