[Mono-osx] Potential missing symlink creation issue for 2.6.4_3

Michael Hutchinson m.j.hutchinson at gmail.com
Fri Apr 30 16:08:57 EDT 2010

On Fri, Apr 30, 2010 at 1:41 PM, Gregory Smith <wolfy at treellama.org> wrote:
>> The symlink should work, but I'd recommend explicitly invoking
>> /Library/Frameworks/Mono.framework/Versions/Current/bin/mono, or even
>> a specific version, so that you can guarantee which Mono you're
>> running with. We've seen problems where a user would install Mono from
>> Macports, which would be in the path, and would lack expected
>> libraries or have other problems.
> macpack uses `which mono` which seems to me like it wouldn't work if
> /usr/bin/mono weren't present.

Correct. /usr/bin/mono *should* be present - if it isn't, then there's
a regression in the Mono packages.

>> You can find a more robust launch script and more explanations here:
>> http://mjhutchinson.com/journal/2010/01/24/creating_mac_app_bundle_for_gtk_app
> Seems like a lot of this would be useful to have in macpack? I see it sets

Right, but macpack isn't actively developed.

> DYLD_FALLBACK_LIBRARY_PATH, which might fix the aforementioned
> System.DllNotFoundException: libgtk-quartz-2.0.0.dylib problem that has been
> in the last couple releases. Since I use stock macpack, I've had to tell
> users to go back to 2.4.3.
> Still, it would be nice to have a deprecation notice before breaking stuff
> like this.

That sounds like a bug, not intentional breakage. Have you reported it
on bugzilla?

Michael Hutchinson

More information about the Mono-osx mailing list