Package: pinentry
Version: 0.7.5-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080318 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:
> cc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/gtk-2.0 
> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libpng12    -I../secmem -I../pinentry 
> -Wall  -g -Wall -O2 -Wall -Wcast-align -Wshadow -Wstrict-prototypes 
> -Wno-pointer-sign -c gtksecentry.c
> In file included from /usr/include/gtk-2.0/gtk/gtkactiongroup.h:34,
>                  from /usr/include/gtk-2.0/gtk/gtk.h:38,
>                  from gtksecentry.c:40:
> /usr/include/gtk-2.0/gtk/gtkitemfactory.h:50: warning: function declaration 
> isn't a prototype
> gtksecentry.c:274: error: conflicting types for 'g_malloc'
> /usr/include/glib-2.0/glib/gmem.h:47: error: previous declaration of 
> 'g_malloc' was here
> gtksecentry.c:292: error: conflicting types for 'g_malloc0'
> /usr/include/glib-2.0/glib/gmem.h:48: error: previous declaration of 
> 'g_malloc0' was here
> gtksecentry.c:312: error: conflicting types for 'g_realloc'
> /usr/include/glib-2.0/glib/gmem.h:50: error: previous declaration of 
> 'g_realloc' was here
> make[3]: *** [gtksecentry.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/03/18

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to