grig version 0.7.2-4 failed to build on amd64 with GCC-4.6/oneiric

[Matthias Klose]

grig version 0.7.2-4 failed to build on amd64 with GCC-4.6/oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2452090

Details about the rebuild:
https://lists.ubuntu.com/archives/ubuntu-devel/2011-April/033042.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2452090/+files/buildlog_ubuntu-natty-amd64.grig_0.7.2-4_FAILEDTOBUILD.txt.gz

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

   * DH compat level 5 (no change)
   * Standards-level 3.9.0 (no change)
   * Added dependency on ${misc:Depends}.
   * debian/watch: use sf redirector.
   * Removed empty postinst and postrm from the source package
   * debian/rules: link config.{guess,sub} from autotools-dev in the
     config.status target, restore in the clean target. Remove diff
     concerning config.{sub,guess} from patch debian-changes-0.7.2-4.
   * debian/copyright: proper copyright notice!
Checksums-Sha1:
 f217dc9dfa1dc2cea845fc3d4ca719f1dbaa1091 109516 grig_0.7.2-4_amd64.deb
Checksums-Sha256:
 339673f220c4f598839cf354ad849ce239785b0d210a6ab8b76bb4a132c4b8ef 109516 grig_0.7.2-4_amd64.deb
Files:
 383d66f6a5ccf67fadac42805fcf2b33 109516 hamradio optional grig_0.7.2-4_amd64.deb

******************************************************************************
Built successfully
Purging chroot-autobuild/build/buildd/grig-0.7.2

[Kamal Mostafa (kamalmostafa)]

grig (0.7.2-4) seems to build fine in Oneiric now, with the stock toolchain. I'm marking this as "Won't Fix". Please advise if my analysis here is incorrect.

Builds fine with:
gcc: Installed: 4:4.6.0-5ubuntu1
gcc-4.6: Installed: 4.6.1-2ubuntu2
binutils: Installed: 2.21.52.20110707-1ubuntu1
(all newer versions than the https://launchpad.net/~ubuntu-toolchain-r/+archive/test toolchain for which the FTBFS was reported).

[Andreas Moog (ampelbein)]

The problem is this:

Function `gdk_gc_new' implicitly converted to pointer at rig-gui-lcd.c:371
Function `gdk_gc_new' implicitly converted to pointer at rig-gui-smeter.c:564

Our automated build log filter detected the problem(s) above that will
likely cause your package to segfault on architectures where the size of
a pointer is greater than the size of an integer, such as ia64 and amd64.

This is often due to a missing function prototype definition.

Since use of implicitly converted pointers is always fatal to the application
on ia64, they are errors. Please correct them for your next upload.

More information can be found at:
http://wiki.debian.org/ImplicitPointerConversions

[Kamal Mostafa (kamalmostafa)]

Ok, I have fixed this in Debian's grig (0.7.2-5):
http://packages.qa.debian.org/g/grig/news/20110711T204950Z.html

Ubuntu PPA build (with stock toolchain):
https://launchpad.net/~kamalmostafa/+archive/grig

Sync request to be filed shortly.

[Launchpad Janitor (janitor)]

This bug was fixed in the package grig - 0.7.2-5

---------------
grig (0.7.2-5) unstable; urgency=low

  * Do not define GDK_DISABLE_DEPRECATED since we do use deprecated
    gdk calls and need their prototypes (LP: #770765).
  * Clean up debian/patches; do not patch in intltool-*.
  * New Debian maintainer (Closes: #553658).
 -- Kamal Mostafa <email address hidden> Wed, 13 Jul 2011 10:46:36 +0000