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.228144
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 ... 12 13 14 15 16 17 18 19 20 21 22 ... Next › Last »

WoefulDerelict commented on 2017-02-21 18:55

billypilgrim: The current most likely suspect is a race condition in QT4's build system. Have you tried building this in a clean chroot to eliminate the possibility this is the result of some unexpected interaction with some package installed on your system?

kabbalah commented on 2017-02-21 18:49

Thank you install skype and aur low one time the lib32-qt4 there was no longer need to compile

billypilgrim commented on 2017-02-21 18:49

I tried building it outside of /tmp but it failed. This time it was with the same error as I had the first time, which makes me think building in /tmp was a secondary reason why it fails.

Log is here:

WoefulDerelict commented on 2017-02-21 18:44

ranger: That is understandable. Your input is appreciated.

kabbalah: The error proper is further back in the build output and I'd wager it looks something like this: helpviewer_qwv.cpp:161:1: error: expected class-name before ‘{’ token

ranger commented on 2017-02-21 18:43

I have limited space in my main pc, that's why I use /tmp.
I will try tomorrow to unmount /tmp and build again.

kabbalah commented on 2017-02-21 18:42

This is error in compile lib32-qt4.:

make[4]: *** [Makefile:14143: .obj/release-shared/helpviewer_qwv.o] Error 1
make[4]: se sale del directorio '/tmp/yaourt-tmp-julio/aur-lib32-qt4/src/qt-everywhere-opensource-src-4.8.7/tools/assistant/tools/assistant'
make[3]: *** [Makefile:42: sub-assistant-make_default-ordered] Error 2
make[3]: se sale del directorio '/tmp/yaourt-tmp-julio/aur-lib32-qt4/src/qt-everywhere-opensource-src-4.8.7/tools/assistant/tools'
make[2]: *** [Makefile:113: sub-tools-make_default-ordered] Error 2
make[2]: se sale del directorio '/tmp/yaourt-tmp-julio/aur-lib32-qt4/src/qt-everywhere-opensource-src-4.8.7/tools/assistant'
make[1]: *** [Makefile:52: sub-assistant-make_default-ordered] Error 2
make[1]: se sale del directorio '/tmp/yaourt-tmp-julio/aur-lib32-qt4/src/qt-everywhere-opensource-src-4.8.7/tools'
make: *** [Makefile:891: sub-tools-make_default-ordered] Error 2
==> ERROR: Se produjo un fallo en build().
==> ERROR: Makepkg no ha podido compilar lib32-qt4.

WoefulDerelict commented on 2017-02-21 18:39

ranger: Interesting. Thanks for the feedback. Have you tried building it on your main PC outside of /tmp? Unless it is running out of space I can't really imagine why that would effect the build as I've managed to do it here successfully with an i7-870 backed by 16 GB of RAM and inside a VM which was allocated 8 GB.

The best suggestion I've gotten so far is that this is some kind of race condition in qt4's build system which is unfortunate as it is one of the harder things to reproduce reliably, find and fix. Thanks for uploading a binary as I'm sure this will come in handy for some folks.

ranger commented on 2017-02-21 18:19

I still can't build the package using my main pc (i7-3537U, ssd, 8GB RAM) but I managed to build it using my "old" laptop (pentium P6200, 4GB RM).

I don't know why it fails. I have exactly the same makepkg.conf. similar setup and up to date systems. The main difference (except the hardware) is that the laptop doesn't use /tmp for building.

If someone needs the latest version (-8), I uploaded it in the archlinuxgr repo

SigLevel = PackageOptional
Server =$arch

WoefulDerelict commented on 2017-02-21 17:54

kabbalah: You can find old binary releases of lib32-qt4 and many other packages in the Arch Linux Archive:

kabbalah commented on 2017-02-21 17:41

I am installing skype from aur and I have problems with lib32-qt4, this throws an error when compiling, I found a lib32-qt4 at: / I have not used it, I'm waiting to finish compiling the aur.