On Mar 8, 2012, at 04:36, Rainer Müller wrote: > On 03/08/2012 08:25 AM, Konrad Hinsen wrote: >> Thanks! Now I get the log but I don't really understand what's going on: >> >> /usr/bin/cc -dynamiclib -g -O2 -W -Wall -pedantic >> -I/Library/Frameworks/Mono.framework/Versions/2.10.2/include >> -Wl,-single_module registry.o util.o entry.o entryobj.o >> ../cregistry/cregistry.a -o registry.dylib >> -L/System/Library/Frameworks/Tcl.framework/Versions/8.5 -ltclstub8.5 >> -L/Library/Frameworks/Mono.framework/Versions/2.10.2/lib -lsqlite3 >> ld: warning: in >> /Library/Frameworks/Mono.framework/Versions/2.10.2/lib/libsqlite3.dylib, >> file was built for i386 which is not the architecture being linked (x86_64) >> Undefined symbols: >> "_sqlite3_finalize", referenced from: >> _all_objects in util.o >> _all_objects in util.o >> _reg_entry_depends in cregistry.a(entry.o) >> _reg_all_entries in cregistry.a(entry.o) >> ... >> >> Apparently MacPorts picks up an SQLite library from an old Mono >> installation on my machine. But why? And why only now, for the 2.0.4 >> update? And, most importantly, how can I prevent this? > > The Mono framework installs the binary /usr/bin/pkg-config which > announces Mono-related libraries system-wide. This tricks the autoconf > detection of MacPorts to try to link against these libraries from Mono > instead those offered by Apple in /usr/lib. On a blank Mac OS X, there > is no pkg-config. > > Please remove the symlink at /usr/bin/pkg-config. > > There is a existing bug report in the Mono Bugzilla: > https://bugzilla.xamarin.com/show_bug.cgi?id=1154
And an existing MacPorts bug report as well: https://trac.macports.org/ticket/30932 _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
