Package Details: qt4 4.8.7-31

Git Clone URL: https://aur.archlinux.org/qt4.git (read-only)
Package Base: qt4
Description: A cross-platform application and UI framework
Upstream URL: https://www.qt.io
Licenses: custom, GPL3, LGPL, FDL
Conflicts: qt
Replaces: qt<=4.8.4
Submitter: arojas
Maintainer: dviktor
Last Packager: dviktor
Votes: 26
Popularity: 2.51
First Submitted: 2019-05-01 11:51
Last Updated: 2019-07-29 18:11

Dependencies (29)

Required by (677)

Sources (20)

Pinned Comments

dviktor commented on 2019-06-18 12:50

Binary version for latest version (4.8.7-31) with PGP signature is available here

eschwartz commented on 2019-05-09 13:24

@semeion,

qt4 was expelled from the official repositories due to https://lists.archlinux.org/pipermail/arch-dev-public/2019-April/029560.html

It will not be restored, because software needs to stop using qt4. It's fine for people to still use it via the AUR if they have old software that is not ported, but the proper solution is to get that software ported to qt5.

"It takes a long time to compile" is not a reason to move it to community.

@xuanruiqi,

Only Developers and Trusted Users have access to pkgbuild.com, and we will not be uploading qt4 there. If we wanted qt4, we would upload it to community, but we don't -- we have managed to move every package still being actively maintained in the official repos, over to qt5, and we want to stay that way.

...

Again, the proper long-term solution is to get software ported over to qt5.

dviktor commented on 2019-05-05 17:49

For those who have problems with ‘std::tr1’ has not been declared error: build in clean chroot with extra-x86_64-build script.

Latest Comments

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

saverio commented on 2019-05-08 10:37

I tried to build from qt4 (PKGBUILD), but I receive this error during pakages downloading...

==> Making package: qt4 4.8.7-29 (mer 8 mag 2019, 12:34:19) ==> Retrieving sources... -> Downloading qt-everywhere-opensource-src-4.8.7.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 274 100 274 0 0 948 0 --:--:-- --:--:-- --:--:-- 948 100 229M 100 229M 0 0 7662k 0 0:00:30 0:00:30 --:--:-- 5647k ==> ERROR: qtconfig-qt4.desktop was not found in the build directory and is not a URL. ==> ERROR: Could not download sources.

dviktor commented on 2019-05-07 17:10

@semeion this package was removed from official repos and uploaded here. you can set up clean chroot as described here

semeion commented on 2019-05-07 17:08

@dviktor maybe it can be added in mainline arch repository? seems like qt4 could be in mainline/community repo.

I don´t have a clean-chroot environment to compile it. I think alot of users will fail to compile qt4 on next weeks.

dviktor commented on 2019-05-07 16:29

@shaurz please check that you have up-to-date dbus installed on your system

@semeion seems like it's package-related: it's very sensitive for the environment. While for the part of users package builds fine in usual environment the other part suffers from messed env for building Qt4. Even lib32-qt4 package mentions about it and build in clean chroot is recommended

semeion commented on 2019-05-07 16:10

Will this problem be solved in the future? or will it only be possible to compile qt4 using clean-chroot?

shaurz commented on 2019-05-07 10:04

Failing to build with this error:

The QtDBus module cannot be enabled because libdbus-1 version 0.93 was not found. Turn on verbose messaging (-v) to ./configure to see the final report. If you believe this message is in error you may use the continue switch (-continue) to ./configure to continue.

xuanruiqi commented on 2019-05-07 02:56

I have a nonstandard PKGBUILD (my CFLAGS/CXXFLAGS are "-march=native -fomit-frame-pointer -O2 -pipe -fno-plt", but it turned out not to matter. It seems nonstandard PKGBUILD is usually NOT an issue, unless you put questionable things in your CXXFLAGS. Standard optimization options should just be fine.

The real problem is the clean chroot, which usually points to strange bugs.

Do any of us have access to the pkgbuild.com server? If so we can perhaps host built binaries there.

waitnsea commented on 2019-05-06 14:14

@xuanruiqi same result, same opinion : long compilation only possible by clean-chroot, a binary package would be welcome

WFV commented on 2019-05-05 20:45

Was having same issue and editing makepkg.conf made no difference, only lines different from yours were MAKEFLAGS="-j2" and BUILDDIR=/tmp/makepkg aside from PACKAGER and GPGKEY however, builds fine in clean-chroot. Thanks!

dviktor commented on 2019-05-05 17:49

For those who have problems with ‘std::tr1’ has not been declared error: build in clean chroot with extra-x86_64-build script.