Package Details: lib32-qt4 4.8.7-14

Git Clone URL: (read-only)
Package Base: lib32-qt4
Description: A cross-platform application and UI framework (32-bit)
Upstream URL:
Licenses: custom, GPL3, LGPL, FDL
Conflicts: lib32-qt
Replaces: lib32-qt<=4.8.4
Submitter: arojas
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 51
Popularity: 0.786342
First Submitted: 2017-02-09 20:36
Last Updated: 2018-07-10 17:40

Sources (13)

Pinned Comments

WoefulDerelict commented on 2017-03-07 19:07

This package often requires special care to build. If building this with makepkg fails it will be necessary to construct the package in a clean chroot. Using an AUR helper is not recommended; however, aurutils does provide the option to build in the clean chroot.

The process of building this package in a clean chroot is rendered exceptionally simple with the help of scripts in the devtools package and can be completed via the following steps. These summarize the information provided by the Arch Linux DeveloperWiki and assume familiarity with git or the process of downloading a snapshot from the AUR and extracting the archive. Please refer to this article for more information about the devtools scripts and building in the clean chroot: []

Prerequisites: This process uses scripts in devtools to simplify the procedure: please install this package before beginning. The lib32-libmng package is required and must be built or downloaded from the Arch Linux Archive []. QT 4 depends on this package and it is no longer found in the binary repositories.

  1. Clone the lib32-qt4 repository or extract the snapshot archive into a clean working directory.

  2. Enter the directory containing the package source. (PKGBUILD and patches.)

  3. Execute the following command, supplying the location of lib32-libmng: multilib-build -- -I /<somewhere>/lib32-libmng-2.0.3-1-x86_64.pkg.tar.xz

  4. Execute pacman with the -U flag to install the resulting package: just as one would with any other local package. Note: lib32-libmng would need to be installed in a similar fashion if it isn't already present on your system.

WoefulDerelict commented on 2017-02-25 15:52

The QT 4 build system is prone to some odd behaviour: especially if the qtwebkit package is installed. [] []

If your build fails with the following [error: expected class-name before ‘{’ token] when compiling please build in a clean chroot.

If your build fails with error messages about skipping incompatible files and being unable to find a specific file in a compatible format, especially while linking, you will need to build in a clean container to avoid issues.

Building this package in a clean chroot or other form of container will prevent unexpected issues.

All build errors will be ignored unless the build was performed inside a clean, properly configured container. For more information about building in a clean chroot see this article: []

Big thanks to int [at] arcor [dot] de for doing the legwork to track down the relevant issue reports and sending them my way.

The archlinuxgr repository contains a binary copy of this package courtesy of ranger.

[archlinuxgr] Server =$arch

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

samarch commented on 2017-05-17 15:41

Indeed, the compilation is a real pain and takes ages, having the binaries of this package would be nice.

slav commented on 2017-05-13 21:32

Can we put ib32-qt4-4.8.7-13-x86_64.pkg.tar.xz for downloading please?
Thank you

WoefulDerelict commented on 2017-05-13 19:03

Unfortunately I have yet another release and rebuild for you my lovelies. In this release we include a patch to make QT4 play nice with OpenSSL 1.1 and drop the lib32-openssl-1.0 dependency, mirroring the changes in [Extra]. At least thins out the prerequisites. If lib32-qt4 is your only package using lib32-openssl-1.0 it will be safe to remove this package after updating.

ArchRob commented on 2017-05-11 15:39

After hitting a wall with this package twice, I ended up automating the process in a shell script. Public gist here:

Basically, it grabs the latest packages for lib32-libmng and lib32-openssl-1.0, builds them in a clean chroot, then builds this package using the command WoefulDerelict posted in the pinned comment. Helpful, because when I need to update qt4 again in a couple of months, I probably won't remember how I did it the first two times :D

basil commented on 2017-05-06 19:02

I'm confused by the instructions here. I followed the steps up to
multilib-build -- -I /<somewhere>/lib32-libmng-2.0.3-1-x86_64.pkg.tar.xz -I /<somewhere>/lib32-openssl-1.0-1.0.2.k-1-x86_64.pkg.tar.xz
which worked. Now how can I install the package system wide? I went through the devtools Wiki, but it's not clear to me how to proceed. All help is much appreciated.

ranger commented on 2017-05-03 23:34

Again, lib32-qt4-4.8.7-12 has been build and I'm uploading at the moment.

Server =$arch

slav commented on 2017-05-03 22:54

again request to upload please.... lib32-qt4-4.8.7-12-x86_64.pkg.tar.xz

WoefulDerelict commented on 2017-05-03 22:44

PhoenixtheII: Yea, lib32-openssl-1.0 is a new special 1.0 compatibility package that became necessary after lib32-openssl moved to 1.1.0. 1.0 is part of the package's name like the openssl-1.0 package it mirrors in [Extra]. These packages provide support for legacy software that isn't compatible with openssl 1.1.0. It does need to be present in the chroot for this to build against or you'll get an error. Glad you got it sorted. One hopes the update to icu support isn't painful.

PhoenixtheII commented on 2017-05-01 07:22

@WoefulDerelict: Had to manually compile in clean chroot lib32-openssl-1.0 from aur too... *facepalm*

maek commented on 2017-04-30 14:44

@kingcreole: I had your same issue and solved it by purging /var/lib/archbuild