port selfupdate fails

Andrew Long andrew.long at yahoo.com
Tue Aug 16 14:24:26 PDT 2011

On 16 Aug 2011, at 22:01, Eric Cronin wrote:

> On Tue, 16 Aug 2011 16:27:06 -0400, Daniel J. Luke wrote:
>> On Aug 16, 2011, at 4:14 PM, Andrew Long wrote:
>>> <snip/>
>> As far as I know, we don't link with Mono, so it shouldn't interfere
>> with selfupdate (it may interfere with building your own mono). I
>> wasn't sure which was failing for you...
> We don't.  But, the 3rd party Mono package installs in a location that we're searching for libraries in, and it seems ./configure is finding it, and we're preferring it's sqlite library to the system one when building macports base:
> (from an earlier message in the thread):
> ld: warning: in /Library/Frameworks/Mono.framework/Versions/1.9.1/lib/libsqlite3.dylib, missing required architecture x86_64 in file
> So if you move the non-macports Mono out of /Library/Frameworks and selfupdate again it should detect the system libsqlite and be happy.
I've followed the 'uninstall' instructions at mono-project.com (<grin>it isn't *really* a third party mono - it's in fact the one and truly original</grin> and the selfupdate and update outdated has indeed now completed. 

> You don't need to install mono out of ports unless you want mono (macports base does not need it), and installing it out of ports won't solve the problem of the 3rd party libraries in /Library/Frameworks breaking the selfupdate build (you need to remove that directory as suggested above)...

The problem that I now have is to find out which application that, probably several years and several machines ago, caused me to need to install mono framework. But that isn't a problem for this list.

What I think *is* still a question that I an usefully address to the list is this:-

Assuming that I do still need mono for whichever application it was, or that I finally get around to learning .NET from my (seemingly endless) list of self-improvement projects, I can install the macports mono, mono-basic & mono-addins packages. WIll the standard mono development packages then sit happily on top of this? Or am I *still* going to have to struggle with building a universal version from the mono-project source? (which should get rid of the problem that selfupdate is having - only finding an x86 version of the sqlite libraries?)

Regards, Andy

Andrew Long
andrew dot long at yahoo dot com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 275 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110816/10ab0634/attachment.bin>

More information about the macports-users mailing list