[Mono-devel-list] Re: Mono 1.0 binaries available for testing

[Steve Newman]

>From: Ben Maurer <bmaurer at ximian.com>
>To: Mono Development <mono-devel-list at lists.ximian.com>
>Date: Tue, 29 Jun 2004 21:40:37 -0400
>Subject: [Mono-devel-list] Mono 1.0 binaries available for testing
>
>Hey guys,
>
>Miguel just dropped by and asked me to post this.
>
>The packages that we expect to go out for 1.0 are available for
>download. You can find them at:
>
>http://go-mono.com/download2.html
>
>If you have any problems, please do not hesitate to reply.

I've been meaning to try an OS X installation and this announcement finally got me to take action.  The installer ran without a hitch -- thanks to everyone involved in this packaging effort!  However...

There's no visible readme, no instructions in the installer, no obvious information on what to do after installing.  I did a search for the file "mcs" and found it in Library/Frameworks/Mono.framework/Versions/1.0/bin/.  All well and good, so I tried invoking it (with no arguments), and got:

dyld: /Library/Frameworks/Mono.framework/Versions/1.0/bin/mono can't open library: /usr/lib/libiconv.2.dylib  (No such file or directory, errno = 2)

No doubt I'm being quite thick, and my lack of Unix expertise is shining brightly for all to see, but... what exactly do I need to do to actually run the Mono tools on OS X?  For those of us who know C# and the Mac, but don't know Unix, it would be nice to include some brief instructions with the installer.

Additional information:

* I'm running OS X 10.2.8.  It's a fairly vanilla setup for the most part.  At some point in the past I did install Fink, though I've never really used it.

* I searched for files containing "libiconv" in the name.  There is a link named libiconv.2.dylib in /sw/lib, pointing to /sw/lib/libiconv.2.0.4.dylib -- presumably this was part of my Fink installation.  There's nothing resembling a libiconv file in /usr/lib.  Is Fink a prerequisite for installing Mono 1.0?  Any particular version of Fink?  Should I be tweaking my path to reference /sw/lib?

-- Steve