Bug#476295: java-gnome: pango_context_new, pango_font_map_get_shape_engine_type implicitly converted to pointers

[Thomas Girard]

Hello dann,

On Tue, Apr 15, 2008 at 11:00:30AM -0600, dann frazier wrote:
> Our automated buildd log filter[1] detected a problem that is likely to
> 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.
> 
>   Function `pango_context_new' implicitly converted to pointer at generated/bindings/org/gnome/pango/PangoContext.c:34
>   Function `pango_font_map_get_shape_engine_type' implicitly converted to pointer at generated/bindings/org/gnome/pango/PangoFontMap.c:120
> 
> This is often due to a missing function prototype definition.
> For more information, see [2].
> 
> The prototypes for both pango_context_new and
> pango_font_map_get_shape_engine_type are both wrapped in an #ifdef
> PANGO_ENABLE_BACKEND in their respective header files. Perhaps
> defining this at compile time would solve this?
> 
> Though it is guaranteed that this codepath will cause a segfault on certain
> architectures, it is not guaranteed that this codepath would ever be executed
> (e.g., if the returned pointer is never dereferenced). However, this bug
> does prevent the ia64 buildd from successfully building this package, resulting
> in a practical FTBFS issue and warranting the serious severity.
> 
> [1] http://people.debian.org/~dannf/check-implicit-pointer-functions
> [2] http://wiki.debian.org/ImplicitPointerConversions

Thanks a lot for the report and the explanation. That's a very useful
build feature!

I'm working on a fix.

Regards,

Thomas