After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 680866 - Won't build from git without udisk2 version >= 1.97
Won't build from git without udisk2 version >= 1.97
Status: RESOLVED DUPLICATE of bug 680863
Product: gvfs
Classification: Core
Component: build
git master
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2012-07-30 18:43 UTC by Chris Kühl
Modified: 2012-07-31 09:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Require version 1.97 of udisks2 (978 bytes, patch)
2012-07-30 18:43 UTC, Chris Kühl 		none Details | Review

Description Chris Kühl 2012-07-30 18:43:04 UTC 
Created attachment 219928 [details] [review]
Require version 1.97 of udisks2

On gets the error listed below when building with udisks 1.94 for example.

gvfs_udisks2_volume_monitor-gvfsudisks2volume.o: In function `update_volume':
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:229: undefined reference to `udisks_client_get_loop_for_block'
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:367: undefined reference to `udisks_loop_get_setup_by_uid'
gvfs_udisks2_volume_monitor-gvfsudisks2volume.o: In function `ensure_autoclear':
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:912: undefined reference to `udisks_client_get_loop_for_block'
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:916: undefined reference to `udisks_loop_get_autoclear'
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:916: undefined reference to `udisks_loop_get_setup_by_uid'
/home/chris/checkout/gnome/gvfs/monitor/udisks2/gvfsudisks2volume.c:919: undefined reference to `udisks_loop_call_set_autoclear'
collect2: error: ld returned 1 exit status

The attached patch should require the correct version.
Comment 1 Tomas Bzatek 2012-07-31 09:20:41 UTC 

*** This bug has been marked as a duplicate of bug 680863 ***