Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 244 other subscribers

My Favourites



October 2016
« Sep    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current


New multilib packages for slackware-current

 Earlier today, there was a massive update to Slackware-current. The ride was fun, and I am fairly certain we’ll see some breakage. In fact, we found some already and fixed that in a quick update (mounting of Samba shares was broken after splitting the mount utility for Samba shares into its own “cifs-utils” package).

So, what was updated? The highlights of this batch are:

  • the version of the next release is known: it will be “Slackware 14”.
  • kernel is now 3.2.21 – we will likely stick with the 3.2 series since that will get long-term support.
  • KDE moved up to 4.8.4 (meaning that I can remove my own packages for that version from my ktown repository).
  • gcc was bumped to 4.7.1 to accompany the new kernel.
  • glibc was patched to fix a regression
  • python got updated to 2.7.3 (the switch from the old 2.6.x version meant that every package needed to be recompiled which depends on python)
  • the network scripts (rc.inet1) got support for setting up betwork bridges – something I use every day because it allows me to make my Virtual Machines accessible from other computers in my LAN.
  • lots of other individual updates (the complete ChangeLog.txt entry of “Mon Jun 25 05:17:48 UTC 2012” measures more than 300 lines)

And since glibc was rebuilt and gcc updated, I needed to create multilib versions of those.

They can be found here (all of the mirrors below also offer rsync access):


The update to attica-0.4.0 in slackware-current broke many packages of my KDE 4.9-beta2 set. Head over to my other blog post to find out how to fix that easily!

Have fun! Eric


Comment from crond
Posted: June 25, 2012 at 21:55

hi eric,
just now I used slackpkg to update the entire system from stable 13.37 to do KDE4.9 testing.
As of now KDE is 4.8.4
I am facing a issue with that.
In the panel I have
1. kick off application launcher
which is not showing a pop-up menu when I click that. It was ok with Slackware 13.37’s KDE version.
Now, I added
2. Application Launcher, which is working fine.

Comment from crond
Posted: June 25, 2012 at 21:58

hmm…posted in wrong place. re-posted in concern place.
Just ignore the previous post

Comment from Helios
Posted: June 26, 2012 at 12:17

Thank you for the multilib packages.
In kde-4.9.0beta2 , soprano and shared-desktop-ontologies seem newer than in slackware-current. I have not updated them. Should I do itr ?

Comment from Helios
Posted: June 26, 2012 at 12:27

I found also that /usr/bin/superkaramba depends on

Comment from alienbob
Posted: June 26, 2012 at 14:29

Hi Helios

Yes! If you installed KDE 4.9-beta2 you should also update the “deps” which I supplied.

If you find applications in KDE 4.9-beta2 which depend on the older python2.6 then it should be possible to apply the same trick as I described for attica. Multilple python versions can co-exist, and the symlink “/usr/bin/python” will point to the most recent python version which was installed on the system,.


Comment from escaflown
Posted: June 27, 2012 at 03:53

I hope you the KDE rc1 builds will come out soon.

Comment from alienbob
Posted: June 27, 2012 at 14:02


I am already compiling the 4.9-rc1 packages. The sources should see an official release today, but they made the sources available to packagers only one day in advance of release. I may not be ready in time for the official announcement.


Comment from escaflown
Posted: June 27, 2012 at 17:14

Thanks for the hard work Eric! rc1 will help also with the update in -current for those wo don’t ant two maintain two versions of attica and python

Comment from cowlitzron
Posted: June 27, 2012 at 18:32

I made the multilib update. Af first, I held unto the Alien Pastures version of KDE 4.8.4. But, then X wouldn’t start. Then I removed the Alien exclusion from slaptgetrc and did another update which brought in KDE 4.8.4 from Slackware current. I also removed Soprano 2.7.57 and installed Soprano 2.7.6. Now, KDE 4.8.4 is working well and looks to be of final release quality.

Comment from Helios
Posted: June 29, 2012 at 13:45

After upgrading slackware-current and multilib, Acrobat Reader (which is a 32bits program) did not work : was missing. It was not needed before.
I had to “convertpkg-compat32” the package xz and install the resulting package.

Comment from alienbob
Posted: June 29, 2012 at 14:32


Did you also upgrade the compat32 packages? The converted slackware-current package aaa_elflibs-compat32-13.37-x86_64-7.txz contains and the symlink (note that Slackware 13.37 had


Comment from Helios
Posted: June 29, 2012 at 18:14

You are right, I did not install aaa_elflibs-compat32-13.37-x86_64-7.txz, but everything seemed to work well before without it. In fact I have only 3 32bits programs working now : acrobat reader, avast and peazip.

Comment from Abdur-Rahman Rozell
Posted: August 2, 2012 at 17:29

Did a massconvert32 with Slackware64-14B1
install all packages and remastered the iso to do a clean install with the mulitilib packages get the following error with:
cat: can’t open ‘etc/gtk-2.0/’ : No such
file or directory

Comment from alienbob
Posted: August 2, 2012 at 21:13

Abdur-Rahman Rozell,

Don’t worry about that message, it is harmless. The file /etc/gtk-2.0/im-multipress.conf already exists, it is installed by the gtk+2 package and it is removed from the -compat32 package.


Comment from David
Posted: October 16, 2012 at 13:19


I have installed slackware14.0 64bit, I have created 10gb slack.img image and installed custom package for that. It is installed,

While login I am unable to login, getting error.

root@slack1464bit:~# chroot /mnt/slack1464
chroot: failed to run command ‘/bin/bash’: No such file or directory

Thanks for advance.


Comment from alienbob
Posted: October 16, 2012 at 21:25

Hi David

From your story it is not clear what you have installed in that Slackware directory where you are ‘chrooting’ into.
You mention a “custom package” but do not explain any further.

Please open a thread on a Slackware forum like which is more appropriate for generic support questions like your have. My blog is not a support forum really. It does not look like your issue is multilib related.


Comment from David
Posted: October 17, 2012 at 04:12

Dear Eric,

Thanks for your reply,

1. I have installed slackware14.0 (64bit) in my local machine.

2. I have created the 10 gb image space in slackware machine using below command.
(dd if=/dev/zero of=slack14.img bs=1M count=10075).

3. I have format the image (slack14.img). and
mount the slack14.img in /mnt/slack1464.
4. I have installed the custom package through ruby script. The custom package for
installed without any error.

After that While login the mounting image (/mnt/slack1464).

root@slack1464bit:~# chroot /mnt/slack1464
chroot: failed to run command ‘/bin/bash’: No such file or directory

earlier I have created the .img image in (slackware13.1 & 13.37) without any error.

But I am getting the error in Slackware14.0 64bit only.

Thanks for advance.


Write a comment