Skip to main content

digiKam 2.5.0 SlackBuild and GCC 4.7.0

After upgrading to the latest -Current update, one of the LQ member reported that digiKam is once again broken. Since i posted about an update to digiKam SlackBuild which should make digiKam 2.5.0 compilable on Slackware-Current, i'm curious to see if it affected my system. I tested my previous digiKam application on the system that is now running on latest GLIBC and GCC, and it still worked. So, the problem lies during compilation.

So i searched in Google and found this bug report along with the patch used to fix this problem. Right now, i'm working on the updated SlackBuild again and hopefully this time, it compiles perfectly on Slackware Current.

I will make an update to this blog post when i have completed the build process later on.

Update (1:30 PM): I have managed to build digiKam 2.5.0 on Slackware-Current. It seems that it requires some patches because of the changes in GCC and also in Boost which were upgraded few days ago.

So my digiKam SlackBuild is now updated with two additional patches. Please use my updated digiKam SlackBuild and patch1.diff don't forget to download the additional digikam-boost.patch and digikam-gcc4.7.0.patch. Run the SlackBuild and have some snacks because it will require some time to complete.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue