digikam fails to compile
 

Following recent updates, it looked like I need to update Digikam since my existing install won't start because it can't find libmarblewidget. A quick Google suggests that it needs redoing following updates.

When I run digikam's sanity test, I get the message;

The Slackbuild fails as well.

I've built it a couple of times in the past and it's always been fine.

I know there was a recent QT update which might have caused that error to appear but my system's (64 current) up to date.

Any ideas?

have you tried to upgrade to 3.1.0?
i have 3.1.0 running fine even on latest update on Current today

Yes I have. It's more successful with bootstrap.linux (i.e. more output) but still fails with the same error.

EDIT just ran compilation of 3.10 again and got this fail

Do you mind test using my SlackBuilds ?
please make sure you have all the deps installed

you have to recompile OpenCV due to changes in -Current then digiKam will work again :)

Running digiKam 3.10 on Slackware stable with no problem. Used the slackBuild at SlackBuilds.org

Yep, I have digikam 3.1.0 running here on Slackware64-current with all updates up to today, too, and can only recommend all digikam users to upgrade to 3.1.0! Although rebuilding OpenCV took ages, I have already processed 250+ RAW images with the showfoto application, and didn't see any of the annoyances of all previous versions, such as the application not responding for several minutes, just getting slow, or occasionally crashing.

Thanks for making your SlackBuild script available, Willy!

gargamel

Thanks chaps.

EDIT For some reason, it's now compiled without difficulty and works fine - thanks for the help.

I've tried several times to compile OpenCV and it fails each and every time. SBOpkg can't find the source code and returns the 404 error. I found it at the OpenCV site and it took several tries and a long session to finally download the file. It is verison 2.4.4a.

When I run the SlackBuild script it returns the error,

./opencv.SlackBuild: line 65: cd: OpenCV-2.4.4a: No such file or directory

If I change the version number in the SlackBuild script to 2.4.4a it returns the error:

./opencv.SlackBuild: line 65: cd: OpenCV-2.4.4: No such file or directory

Can't win.
:)

use my SlackBuilds :)

I maintain the OpenCV slackbuild @ www.slackbuids.org. Thanks for the heads up, Ill look into the problem.

I compiled OpenCV from source and it worked fine, so you could always give that a go.

Its eaasier to maintain if you want to remove or change the prefix in the future

Thanks, willysr.
Your script and patch worked like a charm.
:hattip:

Fails at the very end with this error

That's another 3 hours I'll never get back again.

Please don't take this the wrong way as I have a great deal of both sympathy and admiration for those who have the time to build from source, including sharing their findings with the wider user base, so many thanks for that.
But I've just grabbed the wifes lappy, and the whole process has taken less than 10 minutes thanks to dependency resolution and a much more widely tested software repository, so am currently using that for my photo management and being able to use the computer for what it's designed for rather than spend hours unproductively waiting for compiling/building only to see it fail is almost pushing me to another distro after more than 8 years of using Slackware. So frustrating that it should all be so difficult and long winded in the 21st century.

By any chance, did you rename the digikam.SlackBuild to another name?

I have found that installations of Digikam and Amarok have failed if I use 'sudo make install' for example instead of 'su' then 'make install'.

If you use slackbuilds, it's supposed to be run using su or su - not sudo

I think he builds and installs directly from source (and I'm wondering how he manages to remove old stuff when he needs to upgrade).

Just guessing based on my own experience, but still hoping it helps vdemuth to track the problem down.

In my experience 9 out of ten such problems are caused by wrong file access mode or user privileges. Just guessing, but did you take into account that digikam.SlackBuild is one of the following?

1. It is readable and has to be called this way:
OR that it is

2. It is readable and executable and thus can alternatively called like so:
Sometimes obsolete stuff in /tmp may cause trouble, so ensure to wipe all stuff related to building digikam from there. Finally, I occasionally had problems on multilib systems, when the build script picked 32-bit libraries, although it was supposed to pick 64-bit stuff. In the last case the only reliable (!) workaround I found was to build the package on a pure 64-bit system and transfer the binary package to the target machine.

gargamel

Yeah, part of his posts seems to suggest this, but then in the error output he has:

Building directly from source wouldn't yield this message, I guess... ;)

gargamel

My only assumption during the process it was moved, deleted, or renamed by other process or he renamed it before the compilation start

How wrong you are:)

Anyway, can't believe I made such a fundamental error, and managed to name the SlackBuild as Slackbuild without the capitalised B.

All up and running now.

Still stand by what I said about things really ought to be simpler in the 21st Century:), but happy it's resolved.

sorry if I wasn't clear, I was responding to willysr following the post by Bazzaah.

Apologies for the mix up this end.

no prob at all, I should have specified that I was referring to him ;) (also gargamel thought I was referring to you)

Less than ideal but I tend just to delete the executable from /usr/bin - a messed up kind of reinstall. That said, the few programs I compile myself work very well and I don't get any error messages so it can't be that bad.

I should learn how to write a couple of SlackBuilds - that would be cleaner and make for easier maintenance.

Let me say I wouldn't count on it at all ;)
This way you will have old versions of stuff (libraries and whatever else get installed besides the binaries) laying around your filesystem and many strange and unexpected things can happen, not to say that it's very difficult to recover a clean installation from this situation.

If you prefer to have a clean system, use only slackbuild scripts to create packages and install those.

I take your points 100% but I only compile Digikam and Clementine so I'm not too worried, most (out of not many) installations I do through sbopkg.

What's the best SlackBuilds tut in your opinion?

In order to keep it 'clean', you can still create a package when installing from source. That way you still keep track of the installed files:

After the usual ./configure and make bit, create a temporary build directory

As root, make install with that build directory as destination

And create a slackware package

Thanks Brox!