digikam 1.0 beta 4 on Slackware64: How?
Hi there,
I'd like to use the latest Digikam version on my Slackware64 box, but somehow I fail to get it working. Apparently this version is not yet supported by SlackBuilds.org, and the SlackBuild script available from slacky.eu fails, even after setting ARCH=x86_64 and changing all entries of i486 to x86_64 in slack-required. It comes a long way, but then fails trying to use/include qt libraries from /usr/lib/ instead of /usr/lib64. Now, this is hopefully not a show stopper, is it? In fact, I suppose there must be some cmake equivalent of the old prefixes as used by the old accord of ./configure;make;make install. But this is my first attempt to compile a KDE 4 application using cmake on Slackware64. Therefore I'd appreciate a hint or two, how to proceed. Thanks a lot Here is what I did and what I get: 1. Download from http://slacky.eu package for i486 and src. 2. In slack-required replace i486 with x86_64. 3. In digikam.SlackBuild change ARCH to x86_64. Result: Code:
Building CXX object digikam/CMakeFiles/digikamcore.dir/__/libs/dimg/filters/hslmodifier.o Thanks for any helpful hint! gargamel |
Did you try my own SlackBuild at http://www.slackware.com/~alien/slackbuilds/digikam/ yet? I have a 0.10.0 package for Slackware64 and that SlackBuild should be easily re-used for the 1.0.0-beta4 source tarball.
Eric |
I've sucessfully used this script for beta3 on Slackware64, I'm assuming nothing too important's changed in between.
Code:
#!/bin/sh Code:
# HOW TO EDIT THIS FILE: |
Quote:
The script fails, unfortunately, with different messages. E. g., at some point it looks for kde-config. I changed this call to kde4-config, but then the script fails later. (Actually, not digikam.SlackBuild fails, but cmake, of course). Instead of trying to fix this I thought it might be better to try out v1.0.0 Beta 4. So far, however, I didn't get it going. gargamel P.S.: I am on Slackware64 13.0 with all official patches applied plus your compat32 multilib enhancements. |
Quote:
Code:
[ 8%] Building CXX object digikam/CMakeFiles/digikamcore.dir/__/libs/dimg/filters/hslmodifier.o gargamel |
Quote:
Could it be, that v0.10 cannot cope with ext4? Guess, I'll have to try some of the command line utilities to, at least, download my photos, just have to find out which one and how. For the longer-term perspective I still hope to get a newer digikamn version working. Thanks so far! gargamel |
Did you try beta3? That compiled and runs fine on my Slackware64 installation with an ext4 filesystem. My camera is auto-detected perfectly, and I can download the photos fine. Might be worth a shot...?
|
Meanwhile I tried to compile a few more packages for x86_64 with the scripts from slackbuilds.org. Some compile flawlessly, but with some, like kipi-plugins and kphotoalbum I have no success, yet. The slackbuilds are denoted to be made for Slackware 13.0, and I thought they should compile properly when I just call the script with
Code:
<program>.SlackBuild -a x86_64 Code:
[ 0%] Generating common/libkipiplugins/svnversion.h gargamel |
I believe the best way to ensure they run with $ARCH as x86_64 is as follows:
Code:
ARCH=x86_64 ./*.SlackBuild sbopkg automatically sets $ARCH to x86_64 if it detects you're running 64bit. |
Quote:
Code:
Building C object CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.o Code:
[ 16%] Building CXX object digikam/CMakeFiles/digikamcore.dir/__/libs/threadimageio/thumbnailcreator.o Also I wonder, if you really used the script unmodified, as ARCH set to i486 means that the result is a 32-bit binary...? gargamel |
Quote:
Probably I misunderstood something regarding command line options. My (obviously wrong) understanding was, that, at least, the scripts provided by Alien Bob interpret parameters such as -a x86_64 or -r 13.0. But this may be only true for his brilliant mirroring script... Not sure, where I got my "understanding" from, originally... gargamel |
The way that SlackBuilds.org SlackBuild scripts are written means that you can pass a variable to the script using the syntax I've shown above without having to edit the actual script itself. Therefore, I don't manually modify the scripts, I just pass certain different options to them using the syntax above. Therefore, to modify the output directory and the build architecture, you could run a script as follows:
Code:
OUTPUT=$HOME/pkgs ARCH=x86_64 ./*.SlackBuild Code:
VAR=${VAR:-somevalue} Code:
# cat ~/.bashrc I'm not in front of my Slackware64 machine, so I can't test the script with beta4, or indeed re-run beta3, but I'll try later on. If you want, I still have the compiled packages for digikam, kipi-plugins and kphotoalbum for 64bit, so I can put those somewhere where you can download them, if you're interested. Also, just a thought, but have you installed the 32bit compatibility libraries on your system? Perhaps there's something messing up the compilation of these packages, because the output you posted above suggests gcc is being called with the options to build 32bit binaries. |
Quote:
Eric |
Quote:
gargamel |
Quote:
Quote:
Quote:
Yes, I have the compat32 provided by Alien Bob stuff installed in my system. But apart from this digikam and kipi-plugins thing, it doesn't seem to cause any trouble. E. g., I was able to compile kaffeine 64bit with no problem using the script from SlackBuilds.org. Although I have meanwhile made it to download my photos from my camera to my computer using gphoto2 I'd still like to find out what's wrong with my system... Thanks for your valued support so far and any further ideas how to track this down. gargamel |
All times are GMT -5. The time now is 04:15 AM. |