GNOME Bugzilla – Bug 596691
Build failure while linking against libcryptui.so
Last modified: 2009-10-10 02:13:54 UTC
Created attachment 144221 [details] [review] Add DBUS_CFLAGS to INCLUDES in libcryptui/Makefile.am This is due to missing DBUS_CFLAGS in INCLUDES. Reproducable with -Wl,--as-needed in LDFLAGS and --enable-tests (so that cryptui-test tries to link against it) libtool: link: i686-pc-linux-gnu-gcc -O2 -march=pentium-m -pipe -ggdb -Wl,-O1 -Wl,--hash-style=gnu -o .libs/cryptui-test cryptui-test-ui.o -Wl,--as-needed /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so /usr/lib/libfontconfig.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libgconf-2.so /usr/lib/libglib-2.0.so ../../libcryptui/.libs/libcryptui.so -pthread ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_proxy_disconnect_signal' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_proxy_new_for_name' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_proxy_call' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_bus_get' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_type_get_map' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_proxy_add_signal' ../../libcryptui/.libs/libcryptui.so: undefined reference to `dbus_g_proxy_connect_signal'
Created attachment 144222 [details] [review] Add DBUS_CFLAGS to INCLUDES in libcryptui/Makefile.am Oops. Incorrect file attached in the previous comment. This is the correct file.
Thanks for looking into the problem. I've committed a slightly different fix in configure.in. commit dc8d28276204dbd9b47e6ff6fb2f3419a648bc1b Author: Stef Walter <stef@memberwebs.com> Date: Fri Oct 9 00:46:38 2009 +0000 Link libcryptui to dbus-glib and dbus Fixes bug #596691
*** Bug 595127 has been marked as a duplicate of this bug. ***