libgwenhywfar version 4.1.0-1 failed to build in oneiric

Bug #831205 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgwenhywfar (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

libgwenhywfar version 4.1.0-1 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2700958

Details about the rebuild:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2700958/+files/buildlog_ubuntu-oneiric-amd64.libgwenhywfar_4.1.0-1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 2196 lines into the build log:

qt4dialogbox.hpp:14:19: fatal error: QDialog: No such file or directory
compilation terminated.
make[5]: *** [qt4dialogbox.lo] Error 1
make[5]: Leaving directory `/build/buildd/libgwenhywfar-4.1.0/gui/qt4'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/build/buildd/libgwenhywfar-4.1.0/gui/qt4'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/build/buildd/libgwenhywfar-4.1.0/gui'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/libgwenhywfar-4.1.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/libgwenhywfar-4.1.0'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110821-1858
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/libgwenhywfar-4.1.0

Tags: ftbfs oneiric
Matthias Klose (doko)
Changed in libgwenhywfar (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Micha Lenk (micha) wrote :

Just tried it on my own with libgwenhywfar 4.1.0-1: fails to build (confirmed)
and with libgwenhywfar 4.2.1-1 from Debian: fails to build too. :(

Revision history for this message
Micha Lenk (micha) wrote :

The build already fails at configure stage:

checking if QT4 is allowed... yes
checking for qt4 includes... -I/usr/include/qt4 -I/usr/include/qt4/Qt -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
checking for qt4 libraries... not found
checking for qt4 moc... /usr/bin/moc-qt4
checking for qt4 uic... /usr/bin/uic-qt4
configure: WARNING:
 QT4 is not explicitly disabled and I could not find some QT4 components
 (see which are missing in messages above).
 If you don't want to compile QT4 applications please use "--disable-qt4".

Revision history for this message
Micha Lenk (micha) wrote :

Adding --with-qt4-libs=/usr/lib/i386-linux-gnu to the configure flags fixes the build for i386, so it seems an issue caused by missing support for multi-arch by the Gwenhywfar build system.

Revision history for this message
Micha Lenk (micha) wrote :

The attached patch should fix the build failure.

The patch cannot be uploaded to Debian yet, because on Debian systems the Qt libraries still live in /usr/lib (the single arch path), and the additional flag causes the build system to look in the specified directory only.

A better fix (auto Qt path discovery for both, single arch and Multiarch) is already committed to the upstream SVN, so the next upstream version will not need this patch.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgwenhywfar - 4.1.0-1ubuntu1

---------------
libgwenhywfar (4.1.0-1ubuntu1) oneiric; urgency=low

  * Explicitly configure for qt multiarch location (Micha Lenk). LP: #831205.
 -- Matthias Klose <email address hidden> Mon, 19 Sep 2011 22:46:33 +0200

Changed in libgwenhywfar (Ubuntu Oneiric):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.