GNOME Bugzilla – Bug 335475
vte does not compile
Last modified: 2006-04-28 07:32:17 UTC
Please describe the problem: On my system, an old version of gnome is installed, with a libzvt library in it. Vte finds this library and tries to link to it, but this old libzvt library is linked to old pango, gtk, and glib libraries. This results in a linker error. Since vte doesn't have a --without-libvte or similar switch, the simplest solution for me was to add libzvt to garnome and make vte dependent on it. This way, a new libzvt is compiled that is linked to the new gtk, glib an pango libraries, and vte compiles and links just fine. Steps to reproduce: 1. make paranoid-install in the desktop dir, with an old gnome including libzvt installed 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Created attachment 61750 [details] [review] Patch to include libzvt in garnome
Thanks Armin. :) However, I rejected this particular patch, because libzvt definitely does not belong in the desktop/ meta garball. This is pretty much for the official GNOME Desktop packages only. If at all, this one belongs to bootstrap... Anyway, I believe the real issue probably is somewhere else. Why was that partciluar version picked up anyway? Where exactly is it located? FWIW, I do have a bunch of previous GNOME versions installed. They do not interfere, and old installations are not picked up by a new one. Did you have some stale env vars set, by any chance? Like building GARNOME running inside a previous installed GARNOME? I recall some env variables have been causeing issues in the past. That was back the days I switched to building in a virtual console only, rather than a terminal on the desktop... I guess the most important question is, why this particular lib was picked up. Do you have this lib installed in multiple versions, including one by your distro? What distro is this?
GAR. Forgot to set to NEEDINFO. :)
I am sorry, the problem was that I messed around with some paths in the gar.conf.mk file, it was entirely my own fault. I feel a bit foolish now for reporting this as a bug. Thanks for the help!