Package: src:qt4-x11 Version: 4:4.8.2+dfsg-4 Severity: important Tags: moreinfo
Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com>wrote to debian-i...@lists.debian.org, i...@buildd.debian.org, pkg-kde-t...@lists.alioth.debian.org
on Sat, 8 Dec 2012 21:33:30 -0300:
Please keep pkg-kde-t...@lists.alioth.debian.org CCed, we are not subscribed to this lists. Thanks!Hi ia64 porters/buildd maintainers! I'm writing you because of the strange FTBFS we have for qt4-x11 [0], which are normally solved by doing a give-back until it builds :-/ .It's not the first time we see this, and as in other ocassions, we have accessed a porter machine (merulo.debian.org) to try to determine what's going on. "Saddly" all we could do is sucessfully build the packages. We could not reproduce the bug in any way :-(This last time Pino Toscano tried three times and one myself. You can get the compressed log from my build from [1].I would like to know if there is something else we/you can try to solve this issue. Maybe it only triggers inside sbuild?This is the only issue that keeps some security fixes of Qt out of wheezy, and so it would be really great if we can find a way to solve this FTBFS.[0] <https://buildd.debian.org/status/logs.php?pkg=qt4-x11&arch=ia64> [1] <http://perezmeyer.com.ar/temp/qt4_x11_buildlog.txt.xz> -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
The tail of the most recent build log: cd src/corelib/ && make -f Makefile installmake[3]: Entering directory `/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg/src/corelib' g++ -c -include .pch/release-shared/QtCore -g -O2 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/ia64-linux-gnu/glib-2.0/include -O2 -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC -DQT_SHARED -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DELF_INTERPRETER=\"/lib/ld-linux-ia64.so.2\" -DQLIBRARYINFO_EPOCROOT -DQT_USE_ICU -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtCore -I.rcc/release-shared -Iglobal -I../../tools/shared -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4 -I.moc/release-shared -o .obj/release-shared/qlibraryinfo.o global/qlibraryinfo.cpp
cc1plus: error: one or more PCH files were found, but they were invalid cc1plus: error: use -Winvalid-pch for more information cc1plus: fatal error: .pch/release-shared/QtCore: No such file or directory compilation terminated. make[3]: *** [.obj/release-shared/qlibraryinfo.o] Error 1make[3]: Leaving directory `/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg/src/corelib'
make[2]: *** [sub-corelib-install_subtargets-ordered] Error 2make[2]: Leaving directory `/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg' dh_auto_install: make -j1 install DESTDIR=/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no INSTALL_ROOT=/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg/debian/tmp/ returned exit code 2
make[1]: *** [override_dh_auto_install] Error 29make[1]: Leaving directory `/build/buildd-qt4-x11_4.8.2+dfsg-4-ia64-CRoDdA/qt4-x11-4.8.2+dfsg'
make: *** [binary-arch] Error 2I couldn't figure out yet what is really going on with the package on the buildds, and why g++ refuses the precompiled header file (pch).
It builds fine on my box. Machine: Dell PowerEdge 3250 Processor: 2x Itanium Madison 1.5GHz 6M Memory: 16G I suggest doing the following:- Please could you make a new dfsg version of the qt4-x11 package for unstable. Please apply both attached patches. - The patches won't fix the problem, but we'll get a more verbose error message when it fails next time on the buildd.
The patch revert_ia64-remove-parallel.patch reverts the removal of the dh --parallel switch on ia64 which you have done with version 4:4.7.4-1 a year ago. The patch add-winvalid-pch.patch adds the -Winvalid-pch switch to any g++ and gcc invocation that uses a pch file. This should give us the reason why the compiler doesn't recognize the pch.
This shouldn't have any side effect to the other archs than ia64. I'll watch out the buildd log of the next dfsg version of the package. Stephan
revert-ia64-remove-parallel.patch
Description: revert-ia64-remove-parallel.patch
add-winvalid-pch.patch
Description: add-winvalid-pch.patch