Slackware 13.37 and Qt3 | Niels Horn's Blog

Niels Horn's Blog

Random thoughts, tips & tricks about Slackware-Linux, Lego and Star Wars

Slackware 13.37 and Qt3

Slackware_buttonA few days ago the first release candidate of Slackware 13.37 was announced. I updated my -current box and started testing it the same day and until now all seems fine.

I also changed to the nouveau video driver, substituting the closed-source blob from nVidia, using the mesa-7.10 library that sits in /testing for now.
Why use closed-source programs if open-source alternatives are available? :)

After updating my installation, I started to test some of my SlackBuilds and noticed that Patrick had decided to drop the kde3-compat packages only a few days earlier… This meant that some of the older programs I use, based on Qt3, would not run any longer! Personally I use QCad and CdCat that are in this category, but a quick check in showed several others that have Qt3 as a dependency still.
OK, they are older programs, but some of them still have their value and probably other people still use them as well.
So is this a big problem? Well, not really…

My private Qt3 package

I have been using my own Qt3 package for a while, as the original version in /extra/kde3-compat was built before the change to libpng-1.4.x and libjpeg-v8* in Slackware. It was basically a simple re-build with a patch to use the newer png library. I used the original SlackBuild script from the 13.1 tree, with a little hack to include the patch.
So I thought it would be nice to submit the SlackBuild for others to build the Qt3 package as well. But there was a problem with that script…


Pat Volkerding’s SlackBuild to build the Qt3 package contains some serious wizardry to get it to work – caused by the complexity of the Qt3 sources. The biggest problem was that it builds in /opt, not in the normal /tmp directory. This is OK if you build the package on a guaranteed clean machine or a virtual machine. But not on a box where other programs are already installed…
It took me some serious hair-pulling to understand what was going on and several failed attempts, but in the end I was able to dissect all the wizardry and build the Qt3 package in /tmp/SBo, as is the standard for packages on

The result is closed for submissions at the moment, preparing for the new Slackware release, so I cannot submit the script there yet.
But if you are running the Slackware 13.37 Release Candidate yourself and want to test some of the programs that need Qt3, you can download the SlackBuild for it (or pre-built packages) from my site.
For now it’s the only package for Slackware 13.37 but the rest will follow after the official release ;)

Bookmark and Share

This entry was posted on Sunday, March 13th, 2011 at 0:31 and is filed under Slackware. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “Slackware 13.37 and Qt3”

  1. PICCORO Says:

    i analisys the all patchs ovber slack package and many implementatios are worng, please many flags u may consider that configure script override this settings, and also the pro files inside every directory are set own cflags psrding option!

    some others are old and buggy, like qt-x11.diff that forces qt3 to build gif support , this are property setr using configure options! (and also override this patch)

    The correction s are made at Mckay blog anunce of qt3. please consider to use this tarball and revise patchs!

  2. Niels Horn Says:

    Not sure if I understood you completely, but my strategy was to make a package as compatible as possible with the original Slackware package created by Pat Volkerding.
    I did not intend to be too intrusive and wanted to make sure that everything just continued working as it has been for several years.
    So this meant using the same patches that have been used for years.

    The general idea was to maintain compatibility with older packages that still need Qt3, not to create something more modern.

    The only changes I applied were related to the way it is built and where it is build, to follow the general rules / guidelines.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

It may take some time for your comment to appear, it is not necessary to submit it again.