[Bug 755222] cerbero: gettext-tools compilation failure on mingw

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755222

--- Comment #6 from Philippe Renon <philippe_renon at yahoo.fr> ---
Well, I was happily compiling and coding with gstreamer 1.5.x with msys/mingw
until gettext-tools version got bumped from version 0.19.4 to 0.19.5.1 (see
http://cgit.freedesktop.org/gstreamer/cerbero/commit/?id=ff87925304c88f15e814f34bea010d5ecf5d5d71).

After that version bump, I started seeing the compilation error shown in first
message in this bug report. The error happens when doing "cerbero bootstrap".

The duplicate definition comes from
.\cerbero\mingw\w32\i686-w64-mingw32\include\stdio.h

Here is a relevant extract:

#if __USE_MINGW_ANSI_STDIO
/*
 * User has expressed a preference for C99 conformance...
 */

[SNIP]

static __attribute__ ((__unused__))
__attribute__ ((__format__ (gnu_printf, 2, 3))) __attribute__((nonnull (1,2)))
int asprintf(char **__ret, const char *__format, ...)
{
  register int __retval;
  __builtin_va_list __local_argv; __builtin_va_start( __local_argv, __format );
  __retval = __mingw_vasprintf( __ret, __format, __local_argv );
  __builtin_va_end( __local_argv );
  return __retval;
}

[SNIP]

#endif /* __USE_MINGW_ANSI_STDIO */


Another relevant part is found in .\mingw\w32\i686-w64-mingw32\include\_mingw.h

#if defined(_POSIX) && !defined(__USE_MINGW_ANSI_STDIO)
/* Enable __USE_MINGW_ANSI_STDIO if _POSIX defined
 * and If user did _not_ specify it explicitly... */
#  define __USE_MINGW_ANSI_STDIO            1
#endif



Now I am not sure why the issue started but adding the patch addresses it.
With the patch I am able to run "cerbero bootstrap" and "cerbero package
gstreamer-1.0" to completion.

I am not sure it is the best solution but it does the job...

Something that gets me wondering though is that there is another gettext recipe
that is triggered when running "cerbero package gstreamer-1.0" which compiles
the same version of gettext tool but without any errors.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.