Re: [users@lists.monobjc.net] Re: [us...@lists.monobjc.net] Feeback Wanted on Snow Leopard

[Kenny Clement]

Franky, I've struggled with the same issues. In order to build Mono on Snow Leopard, you need the CFLAGS and CXXFlags set to -m32 for Mono and all the components required for it (gettext, pkg-config, libiconv, glib): example: CFLAGS="-m32" CXXFLAGS="-m32" ./configure --prefix=/mono make make install (note that the prefix should be changed to where-ever you want to install it.) Add the prefix path to your envvar PATH if it is not yet in there. (otherwise it will complain about not finding gettext, ...) In case you get 'deprecated' errors in ucontext, add the following line at the top in /usr/include/ucontext.h: #define _XOPEN_SOURCE 500 (I'm sure there is a better way, but this works for me.) nant is a separate install (build) if you compile Mono: http://www.mono-project.com/NAnt_Installation Hope this helps! - Kenny Franky De Meyer wrote: Thanks for taking the time to  look into this, Laurent, even since it's strictly a Mono problem and not related to MonoBjc. It's much appreciated!!!   I have been trying to test the original fix from Sledge Ham during the weekend, but I'm afraid I'm just not familiar enough with the Mono build procedures.   Here's how far I got so far:   - I have downloaded the Mono tar.gz package and applied the patch in darwin.stop.world.c - I have built Mono, following the guidelines at: http://mono-project.com/Compiling_Mono_on_OSX - This means I now have both the official Mono install, and my own build. - BTW, I only managed to do this on Leopard, the Mono build fails on Snow Leopard. - I followed the guidelines for parallel Mono environments: http://mono-project.com/Parallel_Mono_Environments - I now want to build my monobjc app as a Native app, so that I can copy it to Snow Leopard and test it there. - That's where I'm stuck: my own built Mono version doesn't have everything that monobjc needs to build my app, e.g. there is no "nant" - Next I've been juggling with copying files between my own build and the official install, but gave up. The version numbers of the DLLs/dylibs are not identical and that didn't go well.   So, of course I'm anxious to try out the patches with my own application, but need some guidelines on how to do a monobjc build of a Native app, using the patched Mono build.   Thanks, Franky         From: laurent.etiem...@gmail.com [mailto:laurent.etiem...@gmail.com] On Behalf Of Laurent Etiemble Sent: woensdag 30 september 2009 23:34 To: users@lists.monobjc.net Subject: Re: [users@lists.monobjc.net] Re: [us...@lists.monobjc.net] Feeback Wanted on Snow Leopard   Hello,   I have just posted a variant of the fix in Bugzilla. I have only tested it with the sample application. Can someone test it with a larger one ?   With two proposed fixes, the Mono team could take one of them and close this issue.   Regards, Laurent Etiemble. 2009/9/28 Anthony Bowker <anth...@flowol.com> Hello all!   I see that someone has added a possible workaround to the bug# 537764.  I've just been testing my monobjc app on Snow Leopard and, of course, encountered the same problem.  So my great appreciation to Sledge Ham.   It would be awesome to get this fix into Mono 2.6, and I do think this bug is Critical.  I haven't built mono before, and I'm not sure I have a system capable of doing it, but if someone has the relevant binary with the workaround, I would be happy to test it on my systems.   Regards, Anthony   From: laurent.etiem...@gmail.com [mailto:laurent.etiem...@gmail.com] On Behalf Of Laurent Etiemble Sent: Wednesday, September 23, 2009 7:47 AM To: users@lists.monobjc.net Subject: Re: [users@lists.monobjc.net] Re: [us...@lists.monobjc.net] Feeback Wanted on Snow Leopard   Hello, - I have tried the sample app that Kenny has created and I am able to reproduce the crash every time on Snow Leopard. Obsviouly, it seems related to the Mono garbage collection, but I still don't know if Monobjc plays a role. - Has someone been able to create a sample application that crashes without Monobjc ? It surely will boost the reaction on the #537764  entry, if Monobjc is not involved and a simple use-case is provided. - I will try to take time this weekend to play with the sample application, to see if I can narrow further the crash. Regards, Laurent Etiemble. 2009/9/23 Miguel De Buf <miguel.de...@nomadesk.com> Hi Laurent, Did you find some time to look further into the mono/monobjc issue on snow leopard ?  We have someone working on the problem as well (unfortunately no fix yet), so if you want to share some findings, feel free. And very strange, but nobody seems to be interested at the mono side.  The bug report does not show any movement.  Any idea on how we can trigger the nice mono people to look into the issue ? Best regards, Miguel Franky De Meyer wrote: @Laurent: Did you get a chance to try out the modified sample app that Kenny created?   If so, what is your feeling? Does it indeed look like a Mono problem related to garbage collection?   There doesn't seem to be any action in the bugzilla report https://bugzilla.novell.com/show_bug.cgi?id=537764 I have taken the liberty to change the severity to "Major" (actually it should even be "Critical", IMHO), but I get a feeling we may be weeks or months away from a reply or fix. No other developers seem to be confirming the problem, which is weird.   I'm getting more and more questions from users who have upgraded to Snow Leopard and can no longer use our software.   @Kenny: Did you find out anything more on this? Any clues on a work-around.   Thanks all! Franky         From: Kenny Clement [mailto:psyki...@gmail.com] Sent: dinsdag 15 september 2009 19:49 To: users@lists.monobjc.net Cc: psyki.be+nomad...@gmail.com Subject: Re: [users@lists.monobjc.net] Re: [us...@lists.monobjc.net] Feeback Wanted on Snow Leopard   Hi, Me again. I narrowed it down a bit more. I adjusted the SimpleCocoaApp MonoObjc sample. I removed all unrequired stuff, and just kept 1 button connected to an action in HelloController. Clicking the button will open the default about panel, sleep for 1 millisec, and then force Garbage Collection. This ALWAYS causes the crash on Snow Leopard, and works without any issues on Leopard. Note that I didn't do anything with threading (excluding default Mono/MonobjC threads) in this sample. You can find the sample app + sourcecode attached to the original bug report: https://bugzilla.novell.com/show_bug.cgi?id=537764 I hope someone here can help me. Feel free to contact me if there are any questions. Thanks in advance, - Kenny Laurent Etiemble wrote: Hello,   @Franz: - Can you append the stack trace and all the information to the this bug entry (https://bugzilla.novell.com/show_bug.cgi?id=537764) ? - Are you able to get a small sample application (only with the awakeFromNib call) method that exhibits the crash, so I can investigate ?   Regards, Laurent Etiemble. ith any attachments.   -- Miguel DE BUF CTO Error! Filename not specified. Tel. +32 9 233 68 86 Fax +32 9 240 10 39 miguel.de...@nomadesk.com Confidentiality Notice: This message, together with any attachments, is intended only for the use of the individual or entity to which it is addressed. It may contain information that is confidential and prohibited from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination or copying of this message or any attachment is strictly prohibited. If you have received this item in error, please notify the original sender and destroy this item, along with any attachments.     -- Kenny Clement Software Developer Tel. +32 9 233 68 86 Fax +32 9 240 10 39 kenny.clem...@nomadesk.com twitter.com/nomadesk Confidentiality Notice: This message, together with any attachments, is intended only for the use of the individual or entity to which it is addressed. It may contain information that is confidential and prohibited from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination or copying of this message or any attachment is strictly prohibited. If you have received this item in error, please notify the original sender and destroy this item, along with any attachments.