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 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



Multilib Slackware64

By now, the world will be well aware that there was a new release of Slackware Linux last week. Yes, Slackware 13.0 is there… just when I was enjoying a quiet holiday at the french coast. A pity that the release date slipped past the start of my vacation, I always enjoy the virtual “party” when Pat decides to throw the switch.

This also marks the birth of the first stable official release of 64bit Slackware, aka Slackware for the x86_64 architecture, aka Slackware64.  This is a pure-64bit Slackware in the sense that it is unable to compile or run 32bit binaries out of the box. But we took great care to make Slackware64 ready for multilib.  A multilib Linux system has full support for compiling and running both 64bit and 32bit binaries. Pat Volkerding made a decision not to add full multilib capability to Slackware64 initially. Perhaps that will change in future releases.

In the meantime, it is really not hard to add a full multilib layer to Slackware64. The first step would be to build/install multilib versions of gcc and glibc. Then, you have to add 32bit versions of the supporting libraries that your 32bit software will need to run (think of qt, gtk, cups, …. you name it).

Perhaps the mention of “build/install multilib” scared you off?  To make it easy for you, I published a set of pre-built packages that you can install using “upgradepkg –install-new” (gcc and glibc need to be upgraded, the remainder are new packages). You can find those packages at .

To accompany these packages I wrote an article for my Wiki explaining the steps you need to go through.  If you care to give me feedback on my multilib solution, you can do so on the article’s discussion area: .

After completing the intructions, you will have a Slackware system that is capable of building and/or running (among others) Wine, Skype, Citrix client. And many more of course!

Note: if you use slackpkg or another semi-automated package manager, you will have to add the gcc and glibc packages to the update blacklist. If you fail to do so, your package manager will automatically “upgrade” the new multilib gcc and glibc packages to their original pure64 Slackware versions…


Cheers, Eric


Comment from pipes
Posted: December 29, 2009 at 07:51

Thanks man, this rocks 🙂


Pingback from problems with flashplugin in Slackware x86_64 – Page 2
Posted: April 18, 2010 at 01:17

[…] for 64 bit linux is trash. To get decent flash on 64 bit Slack, I installed the multilib files and then installed 32 bit browsers +(Firefox and google chrome from slackbuilds–the 32 bit chrome […]

Pingback from very unusual PATH problems with Slackware64-13.0: No such file or directory
Posted: April 23, 2010 at 02:25

[…] know what? What you say makes a lot of sense. I found this resource online from Alien Pastures: In this article about multilib-slackware64, Eric Hameleers explains that Pat Volkerding wanted a […]

Comment from LucasSimionato
Posted: June 8, 2010 at 20:21

Tks, very good article, I’ll do it on my slck64

Pingback from If Slackware disappeared tomorrow, what would you run? – Page 10
Posted: July 19, 2010 at 19:11

[…] problems you find with Slackware 13.1 x86_64? If you think the multilib is an issue then you should read about what Alien_Bob has presented. As for not having a included install; […]

Write a comment