GNOME Bugzilla – Bug 337993
"neon" support in "gnome-vfs2" fails to build under Mac OS X
Last modified: 2008-09-06 19:10:48 UTC
Building "gnome-vfs2" with "neon" support enabled fails under Mac OS X (10.4.6 on my system): /bin/sh ../libtool --tag=CC --mode=link gcc -pipe -O2 -I/usr/pkg/include -I/usr/include -lresolv -L/usr/pkg/lib -L/usr/lib -flat_namespace -o libhttp.la -rpath /usr/pkg/lib/gnome-vfs-2.0/modules -export_dynamic -avoid-version -module -no-undefined http-neon-method.lo http-proxy.lo -L/usr/pkg/lib -lgobject-2.0 -lgconf-2 -lORBit-2 -lm -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lintl -liconv ../imported/neon/libneon.la ../libgnomevfs/libgnomevfs-2.la libtool: link: warning: `/usr/lib//libiconv.la' seems to be moved rm -fr .libs/libhttp.lax mkdir .libs/libhttp.lax rm -fr .libs/libhttp.lax/libneon.a mkdir .libs/libhttp.lax/libneon.a Extracting /Users/tron/obj/sysutils/gnome-vfs2/work/gnome-vfs-2.14.0/modules/../imported/neon/.libs/libneon.a (cd .libs/libhttp.lax/libneon.a && ar x /Users/tron/obj/sysutils/gnome-vfs2/work/gnome-vfs-2.14.0/modules/../imported/neon/.libs/libneon.a) gcc -pipe -o .libs/libhttp.so -bundle .libs/http-neon-method.o .libs/http-proxy.o .libs/libhttp.lax/libneon.a/ne_207.o .libs/libhttp.lax/libneon.a/ne_acl.o .libs/libhttp.lax/libneon.a/ne_alloc.o .libs/libhttp.lax/libneon.a/ne_auth.o .libs/libhttp.lax/libneon.a/ne_basic.o .libs/libhttp.lax/libneon.a/ne_compress.o .libs/libhttp.lax/libneon.a/ne_dates.o .libs/libhttp.lax/libneon.a/ne_gnomevfs.o .libs/libhttp.lax/libneon.a/ne_locks.o .libs/libhttp.lax/libneon.a/ne_md5.o .libs/libhttp.lax/libneon.a/ne_props.o .libs/libhttp.lax/libneon.a/ne_redirect.o .libs/libhttp.lax/libneon.a/ne_request.o .libs/libhttp.lax/libneon.a/ne_session.o .libs/libhttp.lax/libneon.a/ne_string.o .libs/libhttp.lax/libneon.a/ne_uri.o .libs/libhttp.lax/libneon.a/ne_utils.o .libs/libhttp.lax/libneon.a/ne_xml.o -L/Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgobject-2.0.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgconf-2.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libpopt.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libORBit-2.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgmodule-2.0.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgthread-2.0.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libglib-2.0.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libintl.dylib -lgssapi_krb5 -lkrb5 -lk5crypto -lkrb5support -lcom_err -lresolv /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libxml2.dylib -lz /usr/lib/libiconv.dylib -lm ../libgnomevfs/.libs/libgnomevfs-2.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libbonobo-2.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libbonobo-activation.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libORBitCosNaming-2.dylib /usr/lib/libresolv.dylib /usr/lib//libiconv.dylib /usr/lib/libm.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgnutls.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libtasn1.dylib /usr/lib/libz.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgcrypt.dylib /Users/tron/obj/sysutils/gnome-vfs2/work/.buildlink/lib/libgpg-error.dylib /usr/lib/libc.dylib /usr/bin/ld: Undefined symbols: _ne_xml_dispatch_request _ne_ssl_context_trustcert collect2: ld returned 1 exit status gnumake[2]: *** [libhttp.la] Error 1 gnumake[1]: *** [all-recursive] Error 1 gnumake: *** [all] Error 2 *** Error code 2 The reason is that ne_ssl_context_trustcert() is used in "ne_session.c" but not defined anywhere.
The first missing symbol, _ne_xml_dispatch_request, was fixed in CVS HEAD, but the second was not. In imported/neon/Makefile.am, libneon_la_SOURCES has NEON_SSL_SOURCES, but it is not defined anywhere. NEON_SSL_SOURCES should be set to have SSL-related files (ne_gnutls.c, ne_openssl.c, etc.) and NEON_INCLUDES to have ne_privssl.h.
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together. General further information: http://en.wikipedia.org/wiki/GVFS Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html