Qt 4.4.0-rc1 was released on April, 03. Changes needed to build it are a straightforward modification of qt4-build.eclass, change in QT4_TARGET_DIRECTORIES for qt-gui and added dependency on phonon for qt-qt3support (it is checked for presence on build time). I am currently successfully running it on my ~amd64 system, so it is probably worth consideration for inclusion in the Portage tree. Reproducible: Always Steps to Reproduce:
Created attachment 148982 [details, diff] Patch to make qt4-build.eclass compatible with rc* releases as well
Created attachment 148984 [details, diff] Changes to the qt-gui ebuild as compared to qt-gui-4.4.0_beta1.ebuild
Created attachment 148985 [details, diff] Changes to the qt-qt3support ebuild as compared to qt-qt3support-4.4.0_beta1.ebuild All the other ebuilds are the same as their x11-libs/qt*-4.4.0_beta1.ebuild counterparts except for 's/beta/rc/' in file names.
(In reply to comment #2) > Created an attachment (id=148984) [edit] > Changes to the qt-gui ebuild as compared to qt-gui-4.4.0_beta1.ebuild So which package will install lrelease and lupdate?
(In reply to comment #4) > (In reply to comment #2) > > Created an attachment (id=148984) [edit] > > Changes to the qt-gui ebuild as compared to qt-gui-4.4.0_beta1.ebuild > > So which package will install lrelease and lupdate? > It looks like they simply changed the source directory structure. lrelease and lupdate are no longer in src/, but are installed with qt-gui (from tools/ dir, as far as I remember): alchark@alchark-u3s ~ $ equery f qt-gui | grep lrelease /usr/bin/lrelease alchark@alchark-u3s ~ $ equery f qt-gui | grep lupdate /usr/bin/lupdate
Created attachment 149054 [details, diff] Unset ARCH before compilation It seems that Portage's ARCH variable incorrectly overrides architecture autodetection in the configure script (at least on amd64), which results in Qt being build with 'generic' arch instead of an optimized one, such as x86_64. If the variable is unset prior to compilation, the configure script correctly autodetects x86_64 platform and builds accordingly. I am not sure whether this variable is needed at any point later, but compilation and installation finish fine.
Created attachment 149056 [details, diff] Unset ARCH before compilation (all packages) The aforementioned ARCH issue affects all packages, not only qt-core, so is is better to deal with in the eclass.
Qt-4.4.0-rc1 was added to Portage on April, 10. The ${ARCH} issue is fixed in the updated qt4-build.eclass, so the workaround with unsetting is no longer needed either.
