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 330369 - /libpangocairo-1.0.so: undefined reference to
/libpangocairo-1.0.so: undefined reference to
Status: RESOLVED NOTGNOME
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2006-02-08 09:13 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2006-02-08 10:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stefan Sauer (gstreamer, gtkdoc dev) 2006-02-08 09:13:43 UTC
running a jhbuild on the 8. February result iin these errors when building vte:

libpangocairo-1.0.so: undefined reference to `g_intern_static_string'
libpangocairo-1.0.so: undefined reference to `g_slice_alloc'
libpangocairo-1.0.so: undefined reference to `g_slice_alloc0'
libpangocairo-1.0.so: undefined reference to `g_slice_free1'


(as a side note should, pango not have a cairo-font-backend component ?)
Comment 1 Behdad Esfahbod 2006-02-08 09:32:37 UTC
Linking with the wrong/multiple glib binaries.  Nothing I can fix in Pango...

What do you mean by a cairo-font-backend component?
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2006-02-08 09:56:12 UTC
hmm, in jhbuild is just one glib (its the cvs-version).
And the glib it links against has these symbols in there :(


about the component, I'Ve seen that there is a componen x11-font-backend and though a specific component to libpangocairo might be useful to assign the bug more specifically. Not really important.
Comment 3 Behdad Esfahbod 2006-02-08 10:23:11 UTC
As for glib, it's probably some .la file bringing in the system glib.  Libtool headaches.  What distro are you using?  What do you see in the linker command that fails?  Pasting here may help.

Oh, you mean bugzilla components!  No, not really.  x11-font-backend is there for historical reasons.  Having components for each backend is not *that* usefule.  The problem you are observing for example, is not specific to libpangocairo.  Trying to link libpango will give the same errors too.