GNOME Bugzilla – Bug 154609
Devhelp won't compile (undefined reference)
Last modified: 2005-07-07 22:07:13 UTC
a) compile bootstrap/mozilla b) compile all dependencies for Devhelp (Gtk, etc) c) compile devhelp This will appear : gcc -I/opt/gnome2/include -I/usr/X11R6/include -O2 -pipe -Wall -Wno-uninitialized -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -o .libs/devhelp-bin dh-main.o -Wl,--export-dynamic -L/opt/gnome2/lib -L/usr/X11R6/lib -lm ./.libs/libdevhelp-1.so /opt/gnome2/lib/libgnomeui-2.so -L/usr/lib /opt/gnome2/lib/libgnome-keyring.so /usr/lib/libjpeg.so /opt/gnome2/lib/libbonoboui-2.so -lSM -lICE -lX11 /opt/gnome2/lib/libgnomecanvas-2.so /opt/gnome2/lib/libgnome-2.so /usr/lib/libesd.so /usr/lib/libaudiofile.so /opt/gnome2/lib/libart_lgpl_2.so /opt/gnome2/lib/libpangoft2-1.0.so /opt/gnome2/lib/libgnomevfs-2.so /opt/gnome2/lib/libgconf-2.so /opt/gnome2/lib/libbonobo-2.so /opt/gnome2/lib/libhowl.so -lresolv -lrt /opt/gnome2/lib/libbonobo-activation.so /opt/gnome2/lib/libORBitCosNaming-2.so /opt/gnome2/lib/libORBit-2.so /usr/lib/libpopt.so /opt/gnome2/lib/libgthread-2.0.so /opt/gnome2/lib/libglade-2.0.so /opt/gnome2/lib/libgtk-x11-2.0.so /opt/gnome2/lib/libxml2.so -lz /opt/gnome2/lib/libgdk-x11-2.0.so /opt/gnome2/lib/libatk-1.0.so /opt/gnome2/lib/libgdk_pixbuf-2.0.so /opt/gnome2/lib/libpangoxft-1.0.so /opt/gnome2/lib/libpangox-1.0.so /opt/gnome2/lib/libpango-1.0.so /opt/gnome2/lib/libgobject-2.0.so /opt/gnome2/lib/libgmodule-2.0.so /opt/gnome2/lib/libglib-2.0.so -L/opt/gnome2/lib/mozilla-1.7.2 -lgtkembedmoz -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl -Wl,--rpath -Wl,/opt/gnome2/lib ./.libs/libdevhelp-1.so: undefined reference to `nsCOMPtr_base::assign_from_qi(nsQueryInterface, nsID const&)'
Does this still occur with the devhelp in GARNOME 2.8.1?
No response for months, no complaints either. Report against obsolete GARNOME version. I'm inclined to finally close this bug FIXED...
Suppose this bug actually is fixed. Closing RESOLVED FIXED. If there still is an issue, please reopen this bug.