Package Details: lib32-qt4 4.8.7-15

Git Clone URL: https://aur.archlinux.org/lib32-qt4.git (read-only, click to copy)
Package Base: lib32-qt4
Description: A cross-platform application and UI framework (32-bit)
Upstream URL: http://www.qt.io
Licenses: custom, GPL3, LGPL, FDL
Conflicts: lib32-qt
Replaces: lib32-qt
Submitter: arojas
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 51
Popularity: 0.000000
First Submitted: 2017-02-09 20:36 (UTC)
Last Updated: 2019-11-19 22:10 (UTC)

Pinned Comments

WoefulDerelict commented on 2017-03-07 19:07 (UTC) (edited on 2018-08-26 01:22 (UTC) by WoefulDerelict)

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: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_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 [https://wiki.archlinux.org/index.php/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 (UTC) (edited on 2018-08-26 00:47 (UTC) by WoefulDerelict)

The QT 4 build system is prone to some odd behaviour: especially if the qtwebkit package is installed. [https://bbs.archlinux.org/viewtopic.php?id=132416] [https://bugreports.qt.io/browse/QTBUG-20236]

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: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot]

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 = http://archlinuxgr.tiven.org/archlinux/$arch

Latest Comments

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

kingcreole commented on 2017-04-27 19:58 (UTC) (edited on 2017-04-27 20:35 (UTC) by kingcreole)

that command in a free lib32-qt4 folder fails some update with this output: error: failed to commit transaction (conflicting files) ca-certificates-utils: /etc/ssl/certs/ca-certificates.crt exists in filesystem Errors occurred, no packages were upgraded. ==> ERROR: Aborting... by the way, it even does that when i delete /etc/ssl/certs/ca-certificates.crt

WoefulDerelict commented on 2017-04-26 20:43 (UTC)

It appears that this will need to be rebuilt against icu 59.1 / hunspell 1.6.0. I'll be iterating the package release when these move from testing into the standard repos. If you're using [Mulilib-testing] I'd suggest rebuilding this package against icu 59.1 / hunspell 1.6.0 to avoid issues.

WoefulDerelict commented on 2017-04-26 17:16 (UTC)

darkbasic: One has not found it necessary to build this in a clean chroot unless the system happens to be polluted with .pc files from other bits like qtwebkit that lead to issues. On various test environments I've successfully built this outside a clean chroot. lib32-openssl and lib32-openssl-1.0 are designed to be installed together as lib32-openssl-1.0 (-1.0 is part of the package name) is a clone of openssl-1.0 designed to offer compatibility with legacy software like QT 4 that doesn't support openssl 1.1.0. PhoenixtheII: It looks like your system is out of date and lib32-openssl-1.0 is not installed. The current version of lib32-openssl is 1:1.1.0.e-1. If you do not want to update your system to the openssl 1.1.0 deployment fetch package release 10. Package release 10 will build on openssl 1.0.2 systems.

PhoenixtheII commented on 2017-04-26 16:45 (UTC)

Doesn't build in clean chroot with lib32-openssl-1:1.0.2.k-1-x86_64.pkg.tar.xz installed from aur/lib32-openssl-1.0 error: target not found: lib32-openssl-1.0 ==> ERROR: 'pacman' failed to install missing dependencies. % sudo arch-nspawn /scratch/chroot64/root pacman -Q | grep openssl lib32-openssl 1:1.0.2.k-1 openssl 1.1.0.e-1

darkbasic commented on 2017-04-26 09:45 (UTC)

No I'm building release 11... $ pacaur -Ss lib32-openssl multilib/lib32-openssl 1:1.1.0.e-1 [installato] The Open Source toolkit for Secure Sockets Layer and Transport Layer Security (32-bit) aur/lib32-openssl-1.0 1.0.2.k-1 (18, 15,82) [installed] The Open Source toolkit for Secure Sockets Layer and Transport Layer Security (32-bit) I'm not using a clean chroot because I always managed to build it somehow, even using an AUR helper. Maybe the problem is having both multilib/lib32-openssl and aur/lib32-openssl?

slav commented on 2017-04-25 22:52 (UTC)

@ranger thank you, found now http://archlinuxgr.tiven.org/archlinux/x86_64/

ranger commented on 2017-04-25 22:28 (UTC)

@slav, check my previous comment

slav commented on 2017-04-25 22:03 (UTC)

Can someone drop lib32-qt4 4.8.7-11-x86_64.pkg.tar.xz please? Thank you

ranger commented on 2017-04-25 18:43 (UTC) (edited on 2017-04-25 22:27 (UTC) by ranger)

lib32-qt4-4.8.7-11 as well as lib32-openssl-1.0-1.0.2.k-1 have been uploaded to the archlinuxgr repo. As always, no changes to the PKGBUILD and build in a clean chroot

WoefulDerelict commented on 2017-04-25 17:55 (UTC)

darkbasic: While you are the first user to post a comment with that output it does not seem to be a new issue. If one parses the output correctly it appears that you attempted to build package release 10 against lib32-openssl 1:1.1.0.e which was known not to work. QT4 is not compatible with OpenSSL 1.1.0 and the issue was noted here when OpenSSL 1.1.0 hit testing. Release 11 should work so long as all the prerequisites have been met as it builds against a new lib32-openssl-1.0 package which should provide all the expected symbols.

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