gnome-vfs fails to build

Boey Maun Suang boeyms at macports.org
Mon Sep 10 21:35:52 PDT 2007


Hi Kastus,

On 04/09/2007, at 06:47, Kastus Shchuka wrote:

> [snip]
> gcc  -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 .libs/ 
> libhttp.lax/libneon.a/ne_xmlreq.o   -L/opt/local/lib /opt/local/lib/ 
> libgconf-2.dylib /opt/local/lib/libORBit-2.dylib /opt/local/lib/ 
> libgmodule-2.0.dylib /opt/local/lib/libgthread-2.0.dylib /opt/local/ 
> lib/libgobject-2.0.dylib /opt/local/lib/libglib-2.0.dylib /opt/ 
> local/lib/libintl.dylib -lgssapi -lkrb5 -lasn1 -lcom_err -lcrypto - 
> lroken -lresolv /opt/local/lib/libxml2.dylib /opt/local/lib/ 
> libz.dylib -lpthread -lz /opt/local/lib/libiconv.dylib -lm ../ 
> libgnomevfs/.libs/libgnomevfs-2.dylib /opt/local/lib/libdbus- 
> glib-1.dylib /opt/local/lib/libdbus-1.dylib /opt/local/lib/ 
> libssl.dylib /opt/local/lib/libcrypto.dylib /opt/local/lib/ 
> libhowl.dylib
> /usr/bin/ld: warning -prebind has no effect with -bundle
> /usr/bin/ld: can't locate file for: -lgssapi
> collect2: ld returned 1 exit status
> make[2]: *** [libhttp.la] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2

Have you tried doing a "port clean" after deactivating/removing  
heimdal and before trying to reinstall gnome-vfs?  I think what has  
happened is that gnome-vfs picked up building from where it left off,  
but because heimdal was present at configure time, gnome-vfs found  
heimdal's GSSAPI support and configured itself to link against it,  
which fails once you deactivated heimdal.  "port clean" with take it  
back to the beginning, and so "port install" should then work.

Kind regards,


Maun Suang

-- 
Boey Maun Suang (Boey is my surname)
Email: boeyms at macports dot org






More information about the macports-users mailing list