Hi,

I've been trying to build Nautilus, and it's been going quite well 
except for certain linking errors. The first time through, during one of 
the linking phases I got several hundred "multiply defined" warnings, 
and then "/usr/bin/libtool: internal link edit command failed". No 
undefined symbol errors, nothing else to indicate what actually 
happened, just that. I don't really know what to do about that (maybe 
some max on the number of somethings was exceeded?), but I found this 
message http://sources.redhat.com/ml/gsl-discuss/2001/msg00287.html 
where it was suggested to try adding the --disable-shared parameter to 
./configure, in case it only affected shared libs.

I tried that next, but now I get another error:

% cc -g -O2 -o nautilus **snip lots of .o files** -L/sw/lib **snip lots 
of libs** -lxml

/usr/bin/ld: warning multiple definitions of symbol _locale_charset
/sw/lib/libiconv.dylib(localcharset.lo) definition of _locale_charset
/sw/lib/libintl.dylib(localcharset.lo) definition of _locale_charset
/usr/bin/ld: warning suggest use of -bind_at_load, as lazy binding may 
result in errors or different symbols being used
symbol _locale_charset used from dynamic library 
/sw/lib/libiconv.dylib(localcharset.lo) not from earlier dynamic library 
/sw/lib/libintl.1.dylib(localcharset.lo)
/usr/bin/ld: Undefined symbols:
_xmlFree
_xmlMemStrdup
**more multiple definition warnings**
make[3]: *** [nautilus] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
### make failed, exit code 2

The funny thing is that xmlFree and xmlMemStrdup are (as far as I can 
tell) defined in libxml. Well, they should be at least, and `grep 
_xmlFree /sw/lib/libxml.a` -> "Binary file libxml.a matches". Trying to 
use -bind_at_load as suggested above changes nothing.

Does anybody have any ideas?

Thanks!

Dave


_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to