Source: gnome-vfs Version: 1:2.24.4-2 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H > -I. -I.. -I.. -I.. -pthread -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gconf/2 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -D_REENTRANT > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE > -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE > -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DG_DISABLE_DEPRECATED > -DGNOME_VFS_PREFIX=\"/usr\" -DGNOME_VFS_BINDIR=\"/usr/bin\" > -DGNOME_VFS_DATADIR=\"/usr/share\" -DGNOME_VFS_LIBDIR=\"/usr/lib\" > -DGNOME_VFS_LOCALEDIR=\"/usr/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/etc\" > -DG_LOG_DOMAIN=\"libgnomevfs\" -D_FORTIFY_SOURCE=2 -g -O2 > -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security > -Wall -c -o gnome-vfs-async-job-map.lo gnome-vfs-async-job-map.c > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -pthread > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 > -I/usr/include/p11-kit-1 -D_REENTRANT -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg > -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE > -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT > -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/usr\" > -DGNOME_VFS_BINDIR=\"/usr/bin\" -DGNOME_VFS_DATADIR=\"/usr/share\" > -DGNOME_VFS_LIBDIR=\"/usr/lib\" -DGNOME_VFS_LOCALEDIR=\"/usr/share/locale\" > -DGNOME_VFS_SYSCONFDIR=\"/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" > -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Werror=format-security -Wall -c gnome-vfs-async-job-map.c -fPIC > -DPIC -o .libs/gnome-vfs-async-job-map.o > gnome-vfs-async-job-map.c:30:1: error: unknown type name 'GStaticRecMutex' > gnome-vfs-async-job-map.c:30:45: error: 'G_STATIC_REC_MUTEX_INIT' undeclared > here (not in a function) > gnome-vfs-async-job-map.c:37:1: error: unknown type name 'GStaticMutex' > gnome-vfs-async-job-map.c:37:51: error: 'G_STATIC_MUTEX_INIT' undeclared here > (not in a function) > gnome-vfs-async-job-map.c: In function '_gnome_vfs_async_job_map_lock': > gnome-vfs-async-job-map.c:164:2: warning: implicit declaration of function > 'g_static_rec_mutex_lock' [-Wimplicit-function-declaration] > gnome-vfs-async-job-map.c: In function '_gnome_vfs_async_job_map_unlock': > gnome-vfs-async-job-map.c:172:2: warning: implicit declaration of function > 'g_static_rec_mutex_unlock' [-Wimplicit-function-declaration] > gnome-vfs-async-job-map.c: In function '_gnome_vfs_async_job_callback_valid': > gnome-vfs-async-job-map.c:188:2: warning: implicit declaration of function > 'g_static_mutex_lock' [-Wimplicit-function-declaration] > gnome-vfs-async-job-map.c:202:2: warning: implicit declaration of function > 'g_static_mutex_unlock' [-Wimplicit-function-declaration] > make[4]: *** [gnome-vfs-async-job-map.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/gnome-vfs_2.24.4-2_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
