My thoughts on Slackware, life and everything

Tag: x86_64 (Page 1 of 5)

Updates for LibreOffice and multilib, more to come

libreoffce_logoBecause of recent updates in slackware-current (in this case, the boost package) the LibreOffice in my own repository stopped working. Library conflict. Don’t you love the life on the bleeding edge 😉

By coïncidence, the Document Foundation had just released a new version of their LibreOffice sources, so instead of recompiling the old 5.4.3 packages I could grab the new 5.4.4 release and turn those sources into Slackware packages (Slackware 14.2 and -current). The next major release 6.0 is just around the corner but I am not going to wait for that.
You can get the new packages from my repository – like .

Also, I updated the multilib repository with the latest updates in slackware-current (the new l/Mako, a/lzlib and a/plzip are now also available in a “compat32” version).
Remember to also install the new packages, not just upgrade the existing ones! If you have a local mirror, that means using “upgradepkg –install-new” and if you use slackpkg with slackpkg+, you need to do “slackpkg update; slackpkg install multilib ; slackpkg upgrade-all”. That “slackpkg install multilib” takes care of installing any package you are still missing.

Work on a new Plasma5 package set is also well underway. The 64bit -current bit is done so I know I have my sources and scripts in order, and I am generating a new PLASMA5 Live ISO for testing. Stay tuned.

Slackware has the answer to all

… perhaps even to the Ultimate Question of Life, the Universe, and Everything.

Just kidding of course. From today’s ChangeLog.txt for Slackware “current“:

?Sun Mar 27 08:28:47 UTC 2011
There have been quite a few changes so we will have one more release
candidate:  Slackware 13.37 RC 3.14159265358979323846264338327950288419716.
Very close now!  But we'll likely hold out for

Well there you have it. The answer you all have been looking for, all that time! 😉

The list of changes is again pretty long. It shows that “declaring a Release Candidate” has a good reason. People ask from time to time, why these release candidates? Thy are nothing similar to what the bigger distros use in their progression towards a stable release. Things like “feature freeze” and “show stopper bugs” are used in Slackware development too, but you won’t see those mentioned in the ChangeLog. They are not relating one-to-one to any of the Release Candidates. Instead, the first call of a Slackware Release Candidate causes many people to try and install Slackware-current for the first time in a development cycle. Not many people are anxious to use a development release, especially since all of us keep repeating “when you are running -current, we expect that you know what you are doing, and that you are able to fix a suddenly broken system by yourself (with the help of the community)“. The Release Candidates are a sign of stability for those people. And we need all of you to help with the final stage of development! All these new people testing the pre-release result in many bugs found and forgotten features requested, and this causes a surge in the stabilization process which makes Slackware the rock solid distro we all know.

Multilib fans (slackware64), pay attention!

A new kernel again ( and as the ChangeLog.txt says, there will likely be one more before the final release of Slackware 13.37. This means, you get a recompiled multilib version of glibc from me – and there will be another recompile if we see yet another kernel update.

Grab the updated multilib glibc packages from the usual locations:

Enjoy! Eric

Slackware 13.37 Release Candidate 2

We have progressed to the second release candidate for the upcoming release of Slackware stable (version 13.37 no less). There is probably not going to be a lot of other updates before final release; the TODO list should be quite short now. The only one to know for sure is Pat Volkerding… I am only speculating of course.

Noticable is that the Slackware -current’s kernel has again been updated – this time to And again, as part of a Slackware kernel update, the glibc packages were rebuilt against the new kernel’s header files.

If you have enhanced your 64bit Slackware-current with multilib capabilities, you can upgrade to the new multilib glibc packages that I compiled for you.

Get the glibc packages for your multilib Slackware64-current at as usual (or visit my mirror at

I also updated the content of the slackware64-compat32 directory. In there you will find a copy of all the packages which are created by running the script. Install these packages on top of your multilib Slackware64-current in order to make your computer fully support 32bit applications (or use “upgradepkg –install-new” if you already installed a previous set of these packages).

No idea what I have been talking about?

If you want to know about 64bit Slackware Linux (which is a pure 64bit OS) and how to “upgrade” to a multilib system (supporting 32bit as well as 64bit applications), you should definitelty read


Multilib updates to go with new kernel

Hi folks!

Slackware -current’s kernel has been updated to (something many of you probably did not expect) as part of the large update leading to the first release candidate for Slackware 13.37.

This newer kernel seems to work better on all the developers’ computers especially for X sessions.Also speakup (a kernel driver for speech synthesizers) is now part of the kernel since 2.6.37, which means that a separate kernel containing a speakup patch could be dropped from the installer.

Anyway, as part of the kernel update, Pat Volkerding rebuilt the glibc packages against the new kernel headers.

Those of you who run a multilib-enhanced version of Slackware64 know what that means… I have updated my own multilib repository with rebuilt glibc-2.13 packages. This is not an urgent or mandatory upgrade for you, as the previous version of the multilib glibc packages will probably work fine. But for compiling new software that wants to use the kernel api you’d want to go with the rebuilt versions.

Get the new glibc packages at as usual.

As a bonus, I have also updated my script which is part of the compat32-tools package in the same directory. Several packages have been added for the benefit of compiling and running wine. Please tell me if more packages have to be added to that script!

I also updated the content of the slackware64-compat32 directory which holds a copy of all the packages which are created by running the script (to make it easier for you if you have your doubts about how to use that script).


Updated 64bit packages for libreoffice-3.3.1


Today, uploaded a set of updated packages of libreoffice-3.3.1 for the 64bit Slackware platform. The packages that I had originally made available were sub-optimal.

What happened? When I compiled libreoffice 3.3.1 earlier this week I used two separate (virtual) machines for that, one running 32bit Slackware and the other 64bit Slackware. Somehow I was not paying attention when I copied the results back into my repository and the correct 64bit packages were overwritten by a flawed attempt of a day earlier.

The packages (version “1alien“) that I originally had in the 64bit repository did not include many of the extensions that should have been bundled (the pdf-import, mysql-connector and report-builder modules for instance) and they did not have a working dictionary install routine either.

The updated 64bit packages (version “2alien“) are the good ones. They contain all the extensions, and several dictionaries in the language packs just like the 32bit packages already had. I advise you to upgrade to these versions of libreoffice-3.3.1 for Slackware64! Note that the 32bit packages were alright  from the beginning – they do not need an update.


PS: This is what my Extensions Manager shows now:

« Older posts

© 2024 Alien Pastures

Theme by Anders NorenUp ↑