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 509993 - Vinagre doesn't build against gtk-vnc 0.3.2
Vinagre doesn't build against gtk-vnc 0.3.2
Status: RESOLVED FIXED
Product: vinagre
Classification: Applications
Component: general
git master
Other All
: Normal blocker
: ---
Assigned To: vinagre-maint
vinagre-maint
: 510640 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-16 20:19 UTC by Luca Ferretti
Modified: 2008-01-20 20:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luca Ferretti 2008-01-16 20:19:12 UTC 
vinagre-tab.o: In function `open_vnc':
/home/luca/svn/gnome2/vinagre/src/vinagre-tab.c:258: undefined reference to `vnc_display_set_lossy_encoding'

Please note that in jhbuild we are using the release gtk-vnc 0.3.2
Comment 1 Jonh Wendell 2008-01-16 20:37:13 UTC 
Hi.

Please, use version 0.4 (or use gtk-vnc in development trunk).

I'll release a new revision with these changes as soon as gtk-vnc 0.3.3 is released.
Comment 2 Jonh Wendell 2008-01-19 17:07:44 UTC 
*** Bug 510640 has been marked as a duplicate of this bug. ***
Comment 3 Vincent Untz 2008-01-20 01:13:51 UTC 
Jonh, since vinagre is in the desktop suite and gtk-vnc is an external dependency, we prefer to depend on a released tarball, and not from the current trunk of the dependency. It makes life easier for a lot of people :-)

Anyway, in this case, it might now be simpler to wait for the next gtk-vnc...
Comment 4 Wouter Bolsterlee (uws) 2008-01-20 14:02:59 UTC 
(copying my comments from bug #510640)

It seems that vnc_display_set_lossy_encoding was introduced after the 0.3.2
release: http://gtk-vnc.codemonkey.ws/hg/outgoing.hg/rev/b5de4b4d2c9c

However, the gtk-vnc external dependency for Gnome is set to 0.3.2
(seehttp://live.gnome.org/TwoPointTwentyone/ExternalDependencies for the list).
I think it's not a problem to bump the requirement up, provided there will be a
0.3.3 release REAL SOON NOW, since this dependency is new anyway.
Comment 5 Wouter Bolsterlee (uws) 2008-01-20 14:08:26 UTC 
Reopening since this is still an unsolved issue.

Since Vinagre is in the desktop suite now (great to have it there, btw) the maintainers should make sure the build works with released library dependencies. For now this is not a huge problem, but there is a reason for having a list of supported external dependency versions.
Comment 6 Wouter Bolsterlee (uws) 2008-01-20 14:09:00 UTC 
(This bug can be closed once gtk-vnc 0.3.3 is released.)
Comment 7 Jonh Wendell 2008-01-20 20:03:31 UTC 
I'm sorry for this inconvenience, guys.

I dropped the function call and prefer to wait until gtk-vnc 0.3.3 be released, and approved by release-team to put it back.