Bug#699024: gobject-introspection: FTBFS on x32: Failure of tests/offsets

[Daniel Schepler]

Source: gobject-introspection
Version: 1.32.1-1
Severity: wishlist

>From <URL:http://buildd.debian-ports.org/status/fetch.php?pkg=gobject-introspection&arch=x32&ver=1.32.1-1&stamp=1359195069>:

...
GI_TYPELIB_PATH=:../.. ./gitestoffsets offsets.compiled offsets.introspected
diff -u offsets.compiled offsets.introspected
--- offsets.compiled	2013-01-26 10:08:25.000000000 +0000
+++ offsets.introspected	2013-01-26 10:08:25.000000000 +0000
@@ -5,7 +5,7 @@
 some_enum 48
 some_ptrs 56

-OffsetsBasic: size=80, alignment=8
+OffsetsBasic: size=72, alignment=8
 dummy1 0
 field_int8 1
 dummy2 2
@@ -23,7 +23,7 @@
 dummy8 56
 field_size 60
make[7]: *** [check-local] Error 1
 dummy9 64
-field_time 72
+field_time 68

 OffsetsEnum: size=48, alignment=4
 enum1 0
make[7]: Leaving directory
`/build/buildd-gobject-introspection_1.32.1-1-x32-DaXrjH/gobject-introspection-1.32.1/tests/offsets'
make[6]: *** [check-am] Error 2
...

The cause of this failure is that time_t is 64-bit on x32 while long
is 32-bit.  On the other hand, Offsets-1.0.gir encodes the time_t
field as a glong.

I'm not sure what the proper general fix for this would be.  For now
I'm working around it by just disabling the tests for the upload to
debian-ports/unreleased -- since by the comments, using time_t with
glib is discouraged anyway, and I didn't find time_t issues in any of
the .gir files on my system.

BTW, testing other types in the same place in giscanner/ast.py, I see
that on x32, off_t and dev_t are also 64-bit types.
-- 
Daniel Schepler