GNOME Bugzilla – Bug 681471
3.5.6: configure dependency not bumped
Last modified: 2012-08-14 12:55:26 UTC
During the 3.5.6 cycle, commit 8776700a73f68ac00bf23d846c9158f8e6c1ce35 introduced the new gnome-bluetooth API, but it was forgotten to specify in configure.ac that gnome-bluetooth >= 3.5.5 is required with it, which can result in configure passing but then obscure build failures (like Merging translations into bluetooth-properties.desktop. cc-bluetooth-panel.c: In function 'power_callback': cc-bluetooth-panel.c:359:14: error: 'BLUETOOTH_KILLSWITCH_STATE_UNBLOCKED' undeclared (first use in this function) cc-bluetooth-panel.c:359:14: note: each undeclared identifier is reported only once for each function it appears in cc-bluetooth-panel.c:359:53: error: 'BLUETOOTH_KILLSWITCH_STATE_SOFT_BLOCKED' undeclared (first use in this function) cc-bluetooth-panel.c: In function 'cc_bluetooth_panel_update_power': cc-bluetooth-panel.c:381:2: error: unknown type name 'BluetoothKillswitchState' cc-bluetooth-panel.c:399:15: error: 'BLUETOOTH_KILLSWITCH_STATE_HARD_BLOCKED' undeclared (first use in this function) cc-bluetooth-panel.c: At top level: cc-bluetooth-panel.c:717:7: error: unknown type name 'BluetoothKillswitchState' cc-bluetooth-panel.c: In function 'cc_bluetooth_panel_init': cc-bluetooth-panel.c:822:2: error: 'killswitch_changed' undeclared (first use in this function) make[3]: *** [cc-bluetooth-panel.lo] Error 1 make[3]: Leaving directory `/home/abuild/rpmbuild/BUILD/gnome-control-center-3.5.6/panels/bluetooth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/gnome-control-center-3.5.6/panels' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/gnome-control-center-3.5.6' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.cVkKyt (%build) )
Created attachment 220718 [details] [review] Set gnome-bluetooth requires to 3.5.5
Let me dup my own bug with a newer one, but at least the g-c-c maintainer fixed it already too. Dup of bug 681734 *** This bug has been marked as a duplicate of bug 681734 ***