Source: libphone-ui-shr
Version: 0.1+git20110827-3
Severity: serious
Tags: jessie sid

Hi,

libphone-ui-shr FTFBS when binNMUed against libfso-glib2.

From the amd64 build log:

Making all in src
make[3]: Entering directory `/«BUILDDIR»/libphone-ui-shr-0.1+git20110827/src'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-D_FORTIFY_SOURCE=2 -I../src/util -I../src/widget -I../src/view 
-DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/libphone-ui-shr\" 
-DPACKAGE=\"libphone-ui-shr\" -DLOCALEDIR=\"/usr/share/locale\" 
-DG_LOG_DOMAIN=\"libphone-ui-shr\" -I/usr/include/eet-1 -I/usr/include/fribidi 
-I/usr/include/freetype2 -I/usr/include/p11-kit-1 -I/usr/include/ecore-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/lua5.1 -I/usr/include/embryo-1 -I/usr/include/evas-1 
-I/usr/include/eina-1 -I/usr/include/eina-1/eina -I/usr/include/edje-1 
-I/usr/include/elementary-0   -pthread -I/usr/include/phoneui 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/fso-glib -I/usr/include/fsoframework-2.0 -I/usr/include/libnl3   
-I/usr/include/fso-glib -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -pthread 
-I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libnl3 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   
-I/usr/include/phone-utils -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -g3 -Wall -Wextra -Werror -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c 
-o phoneui-init.lo phoneui-init.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 
-I../src/util -I../src/widget -I../src/view -DDATADIR=\"/usr/share\" 
-DPKGDATADIR=\"/usr/share/libphone-ui-shr\" -DPACKAGE=\"libphone-ui-shr\" 
-DLOCALEDIR=\"/usr/share/locale\" -DG_LOG_DOMAIN=\"libphone-ui-shr\" 
-I/usr/include/eet-1 -I/usr/include/fribidi -I/usr/include/freetype2 
-I/usr/include/p11-kit-1 -I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/lua5.1 
-I/usr/include/embryo-1 -I/usr/include/evas-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -I/usr/include/edje-1 -I/usr/include/elementary-0 
-pthread -I/usr/include/phoneui -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fso-glib 
-I/usr/include/fsoframework-2.0 -I/usr/include/libnl3 -I/usr/include/fso-glib 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libnl3 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/phone-utils -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g3 -Wall -Wextra -Werror -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c 
phoneui-init.c  -fPIC -DPIC -o .libs/phoneui-init.o
phoneui-init.c: In function 'phoneui_backend_init':
phoneui-init.c:63:2: error: 'g_type_init' is deprecated (declared at 
/usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations]
  g_type_init();
  ^
cc1: all warnings being treated as errors
make[3]: *** [phoneui-init.lo] Error 1
make[3]: Leaving directory `/«BUILDDIR»/libphone-ui-shr-0.1+git20110827/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«BUILDDIR»/libphone-ui-shr-0.1+git20110827'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/«BUILDDIR»/libphone-ui-shr-0.1+git20110827'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full logs available via
https://buildd.debian.org/status/package.php?p=libphone-ui-shr

Regards,

Adam

_______________________________________________
pkg-fso-maint mailing list
pkg-fso-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint

Reply via email to