[SOLVED] -current and Digikam

smoooth103 · 04-16-2012, 08:31 PM

So I upgraded to -current a night ago and all is working smoothly until I went to open Digikam. Getting phonon errors and digikam immediately crashes.

Tried to rebuild kipi-plugins but now that won't build (errors out in cmake at kipiplugin_printimages)

Anyone have any guidance on getting digikam (and kipi-plugins) to work on -current?
(any version 1.9.0, 2.5.0+)

willysr · 04-16-2012, 10:22 PM

try my modified SlackBuild http://slackblogs.blogspot.com/2012/...lackbuild.html

smoooth103 · 04-17-2012, 08:14 PM

Willy. I tried your slackbuild for digikam and had no luck. I went back to just trying to build kipi-plugins-1.9.0 but that won't build either!

CMake starts and gets to 10% but bails out when it hits kipi_printimages/dir/wizard.cpp

Best I can tell from slackbuilds.org there are no unusual dependencies for kipi-plugins... is this correct? How can it not build? (the build process identifies all known dependencies found .. "YES")

willysr · 04-17-2012, 09:28 PM

i think probably because of the changes in GLIBC and GCC
I compiled my digiKam using the previous GCC and GLIBC, but after i upgraded both of them, the packages still work.

I will try to rebuilt the package again later on with the latest GLIBC and GCC in -Current.

AFAIK, Kipi-Plugins are compiled within digiKam, so no need to have separate build for digiKam and Kipi-Plugins (if you are using 2.5.0 and above)

tomtomjkw · 04-18-2012, 01:11 AM

I wasn't able to compile digikam, too, but somehow managed to compile working git version of kipi-plugins. Due to completely chaotic nature of proceeding things, I cannot even reproduce the steps I took to achieve it, however 2.6.0 beta 3 version of Digikam is at 58% now, so there is hope that the dreaded printimage plugin compiled finally.

willysr · 04-18-2012, 01:29 AM

See my updated post on digiKam 2.5.0 and GCC 4.7.0 here http://slackblogs.blogspot.com/2012/...d-gcc-470.html

I have updated the SlackBuild and 2 additional patches to work with Slackware-Current

tomtomjkw · 04-18-2012, 02:32 AM

2.6.0 beta 3 has just compiled, so I removed git version of kipi-plugins, installed digikam-2.6.0-beta3, works ok. I'm pretty sure that I used slackbuild from slackbuilds.org with Willy's old patch (http://slackblogs.blogspot.com/2011/...ld-update.html)

willysr · 04-18-2012, 03:00 AM

does it work with GCC 4.7.0 and latest Boost? (1.49)
I haven't tried 2.6.0 Beta 3, but if it works, then it's good then

tomtomjkw · 04-18-2012, 04:24 AM

Yes, it works:

Quote:

tomtom@darkstar:~$ ls /var/log/packages/gcc
gcc-4.7.0_multilib-x86_64-1alien gcc-gnat-4.7.0_multilib-x86_64-1alien gccmakedep-1.0.2-noarch-2
gcc-g++-4.7.0_multilib-x86_64-1alien gcc-java-4.7.0_multilib-x86_64-1alien
gcc-gfortran-4.7.0_multilib-x86_64-1alien gcc-objc-4.7.0_multilib-x86_64-1alien
tomtom@darkstar:~$ ls /var/log/packages/digikam-2.6.0-beta3-x86_64-1_SBo
/var/log/packages/digikam-2.6.0-beta3-x86_64-1_SBo

Need quick hint with boost - no idea how to check the thing

willysr · 04-18-2012, 04:52 AM

probably the patch already applied upstream, so need to add more patches

i'm building it right now

edit: confirmed to work with digiKam 2.6.0 Beta 3 without any need to add patches

smoooth103 · 04-18-2012, 04:28 PM

Thanks guys. I used 2.6.0-beta3 with slackbuilds.org slackbuild -- it appears to be building correctly now. I should have tried the most recent beta version but I thought 2.5.0 would have been the most "stable" release. Thanks for the assistance!

gargamel · 04-21-2012, 09:23 AM

Sorry for bumping a thread already marked as SOLVED, but I seem to miss something. When I try to follow the advice given here, digikam 2.6.0 beta3 appears to compile just fine, but in the end it is not installed, and there's apparently no installable package created. Maybe I understood something not quite correctly.

I did:

(as normal user)
Download digikam-2.6.0-beta3.tar.bz2 from original source
Download and unpack digikam.tar.gz from SlackBuilds.org ==> directory digikam is created with the usual files in it
(all following steps as root)
# mv digikam-2.6.0-beta3.tar.bz2 digikam
# cd digikam
change VERSION to 2.6.0-beta3 in digikam.SlackBuild
same in in digikam.info
empty MD5SUM (I know, it would be better to create a new MD5SUM, but not doing it saves one step of work...

)
install QJson from SlackBuilds.org, as it appears to be a dependency
upgrade opencv from SlackBuils.org to 2.3.1a

and then...

# sh digikam.SlackBuild

As I said, compilation seems to go well, but it ends with the following messages:

Code:

-- Set runtime path of "/tmp/SBo/package-digikam/usr/lib64/kde4/digikamimageplugin_transform.so" to "/usr/lib64/qt/lib"
-- Installing: /tmp/SBo/package-digikam/usr/share/apps/digikam/digikamimageplugin_transform_ui.rc
-- Installing: /tmp/SBo/package-digikam/usr/share/kde4/services/digikamimageplugin_transform.desktop
-- Installing: /tmp/SBo/package-digikam/usr/lib64/kde4/libexec/digikamdatabaseserver
-- Set runtime path of "/tmp/SBo/package-digikam/usr/lib64/kde4/libexec/digikamdatabaseserver" to "/usr/lib64/qt/lib"
cp: cannot stat `AUTHORS': No such file or directory
cp: cannot stat `ChangeLog': No such file or directory
cp: cannot stat `DESIGN': No such file or directory
cp: cannot stat `HACKING': No such file or directory
cp: cannot stat `INSTALL': No such file or directory
cp: cannot stat `tips': No such file or directory
cp: cannot stat `TODO': No such file or directory

No package is created or installed and /tmp/SBo/package-digikam contains only one directory:

Code:

$ ls /tmp/SBo/package-digikam/
usr

What am I missing?

Thanks in advance!

gargamel

smoooth103 · 04-21-2012, 11:04 AM

Use willysr updated 2.5.0 blog post instruction with the two patches. It works.

willysr · 04-21-2012, 11:32 AM

Quote:

Originally Posted by gargamel

Sorry for bumping a thread already marked as SOLVED, but I seem to miss something. When I try to follow the advice given here, digikam 2.6.0 beta3 appears to compile just fine, but in the end it is not installed, and there's apparently no installable package created. Maybe I understood something not quite correctly.

I did:

(as normal user)
Download digikam-2.6.0-beta3.tar.bz2 from original source
Download and unpack digikam.tar.gz from SlackBuilds.org ==> directory digikam is created with the usual files in it
(all following steps as root)
# mv digikam-2.6.0-beta3.tar.bz2 digikam
# cd digikam
change VERSION to 2.6.0-beta3 in digikam.SlackBuild
same in in digikam.info
empty MD5SUM (I know, it would be better to create a new MD5SUM, but not doing it saves one step of work...

)
install QJson from SlackBuilds.org, as it appears to be a dependency
upgrade opencv from SlackBuils.org to 2.3.1a

and then...

# sh digikam.SlackBuild

As I said, compilation seems to go well, but it ends with the following messages:

Code:

-- Set runtime path of "/tmp/SBo/package-digikam/usr/lib64/kde4/digikamimageplugin_transform.so" to "/usr/lib64/qt/lib"
-- Installing: /tmp/SBo/package-digikam/usr/share/apps/digikam/digikamimageplugin_transform_ui.rc
-- Installing: /tmp/SBo/package-digikam/usr/share/kde4/services/digikamimageplugin_transform.desktop
-- Installing: /tmp/SBo/package-digikam/usr/lib64/kde4/libexec/digikamdatabaseserver
-- Set runtime path of "/tmp/SBo/package-digikam/usr/lib64/kde4/libexec/digikamdatabaseserver" to "/usr/lib64/qt/lib"
cp: cannot stat `AUTHORS': No such file or directory
cp: cannot stat `ChangeLog': No such file or directory
cp: cannot stat `DESIGN': No such file or directory
cp: cannot stat `HACKING': No such file or directory
cp: cannot stat `INSTALL': No such file or directory
cp: cannot stat `tips': No such file or directory
cp: cannot stat `TODO': No such file or directory

No package is created or installed and /tmp/SBo/package-digikam contains only one directory:

Code:

$ ls /tmp/SBo/package-digikam/
usr

What am I missing?

Thanks in advance!

gargamel

The slackbuild scripts are usually set to stop whenever they encountered an error on any steps, including missing files on documentation

willysr · 04-21-2012, 11:35 AM

Quote:

Originally Posted by smoooth103

Use willysr updated 2.5.0 blog post instruction with the two patches. It works.

Actually, if you are building 2.6.0 beta 3, you don't need the patches anymore, because the patch has been applied to upstream. You only need my original updated slackbuild, not the latest one.
But since it has been updated now, you can use the slackbuild, but comment out the two lines that tried to apply the patch and you are safe