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.
After yet another hardware problem I have freshly installed Slackware64-13.0, without compat32 stuff. Now Digikam 1.0.0 Beta 4 compiles just fine using both your scripts.
Strange.
I built digikam 1.0.0-beta4 twice on Slackware64 13.0 - first without the -compat32 packages installed, and then again after I installed these multilib packages.
This is the diff from the two log files I captured:
Code:
# diff build64.log build64_32.log
1,3d0
< Source 'digikam-1.0.0-beta4.tar.bz2' not available yet...
< Will download file to /otherhome/slackbuilds/digikam/build
< 2009-09-16 00:20:43 URL:http://kent.dl.sourceforge.net/project/digikam/digikam/1.0.0-beta4/digikam-1.0.0-beta4.tar.bz2 [14116108/14116108] -> "/otherhome/slackbuilds/digikam/build/digikam-1.0.0-beta4.tar.bz2" [1]
Well, with the compat32 stuff installed before the fresh install I tried to compile digikam with three different scripts:
Yours, the one posted by Pwc101 and one available from slacky.eu. The last one is actually even made specifically for digikam 1.0.0 Beta 4, just for 32bit. But all three scripts tried to use 32bit libraries, such as /usr/lib/qt instead of /usr/lib64/qt, although I set ARCH to x86_64 and changed the version.
However, this seems to have been caused by something wrong in my system. Now this all works, and a few snags, cosmetic in nature, are gone, too (e. g. I finally have the name of weekdays in KMail in my language; before everything was translated, even terms like "yesterday", but the weekdays always appeared in English).
I have just installed Alien Bob's digikam package and it seems confused about my locale. The buttons and many of the items on the menus are in Hebrew. Now I do have Hebrew installed on kde as the second language but I have never seen a program do this before. On first running there was a message about the locale having been changed.
digikam 0.10.0 and 1.0.0 beta 4 on 64bit Slackware 13.0
I had no problems compiling digikam on my purelib 64bit Slackware 13.0, without using Slackbuild script at all. I followed official tips in README files, i.e.
Code:
cmake .
make
make install
I had set QTDIR=/usr/lib64/qt prior to compiling.
That way I compiled digikam 1.0.0 beta4 and 0.10.0 as well.
Regarding my problem with the Hebrew buttons - I removed digikam and the Hebrew language kde package and the re-installed digicam and then re-installed Hebrew. Digikam is working properly now.
I suspect that the issue may have been to do with Country/Region and Language in kde system settings. I had British English and Hebrew and no US English. I suspect that digikam did not find 'British English' for some settings and then went down the list to Hebrew. I have re-installed US English as second on the list
Wanted to just give this thread a bump as I've been using the slackbuild in post #3 to successfully install digikam beta5 and now beta6 on slackware-current (32-bit) with KDE 4.3.3 for some time now. Just an FYI in case anyone might be looking for a build script and was not aware. (change to version number was only edit required)
I was also curious to see if there was a reason this was not yet back in the Slackbuilds.org repo. Maybe a problem with the build or the version I have yet to discover. Thought I'd ask here first before posting to the mailing list.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.