Bug 16505 - dbus-c++ fails to build with glib enabled (expat linking problem)
Summary: dbus-c++ fails to build with glib enabled (expat linking problem)
Status: RESOLVED NOTOURBUG
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-24 18:22 UTC by Alexander Svyazin
Modified: 2011-01-05 05:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
patch to add xml libs to examples/glib/dbus-browser build (584 bytes, patch)
2008-06-24 18:24 UTC, Alexander Svyazin
Details | Splinter Review

Description Alexander Svyazin 2008-06-24 18:22:24 UTC
With --enable-glib build fails:

/bin/sh ../../libtool --tag=CXX   --mode=link g++  -fvisibility=hidden -Wall -O3   -o dbus-browser dbus-browser.o xml.o ../../src/libdbus-c++-1.la -lgtkmm-2.4 -lgdkmm-2.4 -latkmm-1.6 -lgtk-x11-2.0 -lpangomm-1.4 -lcairomm-1.0 -lglibmm-2.4 -lsigc-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0   
g++ -fvisibility=hidden -Wall -O3 -o .libs/dbus-browser dbus-browser.o xml.o  ../../src/.libs/libdbus-c++-1.so /usr/lib/libdbus-1.so /usr/lib/libgtkmm-2.4.so /usr/lib/libgdkmm-2.4.so /usr/lib/libatkmm-1.6.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libpangomm-1.4.so /usr/lib/libcairomm-1.0.so -L/usr/lib /usr/lib/libglibmm-2.4.so /usr/lib/libsigc-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libpango-1.0.so /usr/lib/libcairo.so /usr/lib/libfontconfig.so /usr/lib/libfreetype.so /usr/lib/libxml2.so /usr/lib/libglitz-glx.so /usr/lib/libglitz.so /usr/lib/libGL.so /usr/lib/libSM.so /usr/lib/libICE.so /usr/lib/libXmu.so /usr/lib/libXt.so /usr/lib/libXext.so /usr/lib/libXi.so -lpthread /usr/lib/libpng12.so -lz /usr/lib/libxcb-render-util.so /usr/lib/libxcb-render.so /usr/lib/libXrender.so /usr/lib/libX11.so /usr/lib/libxcb-xlib.so /usr/lib/libxcb.so /usr/lib/libXau.so /usr/lib/libXdmcp.so /usr/lib/libpixman-1.so -lm /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so 
xml.o: In function `DBus::Xml::Document::from_xml(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
xml.cpp:(.text+0x1fcd): undefined reference to `XML_ParserCreate'
xml.cpp:(.text+0x1fdb): undefined reference to `XML_SetUserData'
xml.cpp:(.text+0x1ff3): undefined reference to `XML_SetDoctypeDeclHandler'
xml.cpp:(.text+0x200b): undefined reference to `XML_SetElementHandler'
xml.cpp:(.text+0x201b): undefined reference to `XML_SetCharacterDataHandler'
xml.cpp:(.text+0x203b): undefined reference to `XML_Parse'
xml.cpp:(.text+0x2047): undefined reference to `XML_GetErrorCode'
xml.cpp:(.text+0x204f): undefined reference to `XML_ErrorString'
xml.cpp:(.text+0x205a): undefined reference to `XML_GetCurrentLineNumber'
xml.cpp:(.text+0x2064): undefined reference to `XML_GetCurrentColumnNumber'
xml.cpp:(.text+0x206e): undefined reference to `XML_ParserFree'
xml.cpp:(.text+0x20c1): undefined reference to `XML_ParserFree'
collect2: ld returned 1 exit status
make[3]: *** [dbus-browser] Ошибка 1
make[3]: Leaving directory `/home/guybrush/workspace/linkage/dbus-c++/examples/glib'
make[2]: *** [all] Ошибка 2
make[2]: Leaving directory `/home/guybrush/workspace/linkage/dbus-c++/examples/glib'
make[1]: *** [all-recursive] Ошибка 1
make[1]: Leaving directory `/home/guybrush/workspace/linkage/dbus-c++/examples'
make: *** [all-recursive] Ошибка 1
Comment 1 Alexander Svyazin 2008-06-24 18:24:44 UTC
Created attachment 17357 [details] [review]
patch to add xml libs to examples/glib/dbus-browser build
Comment 2 Simon McVittie 2011-01-05 05:05:57 UTC
dbus-c++ <http://sourceforge.net/projects/dbus-cplusplus/> has its own bug
tracker and is no longer hosted here. Please open a bug over there.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.