The parallel library documentation
http://www.mono-project.com/Parallel_Mono_Environments says to set a
environment variable called:
DYLD_LIBRARY_FALLBACK_PATH
But on a mac just setting that environment variable gives me constant
errors until i unset it
I looked up the documentation
I'll re-open them after i figure out why my unit tests fail on windows.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Does anyone have any clue why MonoWrench is queuing, but not building any
Windows builds at the moment? We are looking into upgrading to a newer
build, but can't due to this issue.
We've attempted to build this ourselves before, however we're not sure of
the ideal setup for doing it on Windows.
Hi,
I'll get in touch with the right people internally and see if we can
get this fixed.
Thanks,
Alan
On 11 June 2012 12:11, Filip Lundgren fi...@inkdev.net wrote:
Does anyone have any clue why MonoWrench is queuing, but not building any
Windows builds at the moment? We are looking into
I haven't been able to dig into the code too much yet.. But...
From what i can see XplatUIWin32 only call OnIdle event handlers when
Application.RaiseIdle(EventArgs e) is called by the application.. It
doesn't actually call it when the application goes idle.
I've been researching the Windows
No progress with my floating point issue.
I switch to double in my short test application because they can be at least
correctly printed (but operations like multiplication does not work).
using System;
namespace foobar {
public class foo {
public static void Main(string[]
I also had the problem in mono-2.11.1
Solved with the following patch (also as attachment)
---
*** HttpListenerManager.cs 2012-06-11 17:58:34.0 +0100
--- HttpListenerManager.cs.ORIG 2012-06-11 17:55:46.0 +0100
***
*** 96,108
Hello
I am using mono 2.10.2-5 under centos .
I got a self hosting wcf service that is working fine for some time then
randomly it is crashing the hosting console application with the following
error
Unhandled Exception: System.NullReferenceException: Object reference not set
to an instance
Patch 7 has been pushed
(https://github.com/mono/mono/commit/1743a005ccdc0d8c93795e236d2a5a32043b722c).
Only one left.
Stifu wrote
I'll take care of this soon.
For the record, I'll go ahead and change the visibility of all new test
classes and struct to private. I don't think they need to
I'm getting the following exception sporadically while testing my sample
code that is used as a unit test (though i've never had it fail as a
unit test) both with and without my patch, even with mono 2.10.8 but
this is only happening on Windows...
System.MemberAccessException: Object is busy
In my local copy of mono (robwilkens/mono on github) I can build in
cygwin just fine...
In the real mono/mono, i get the following error:
In file included from ../../eglib/src/glib.h:7,
from socket-io.c:20:
/usr/i686-pc-mingw32/sys-root/mingw/include/stdio.h:536: warning: no
Since no one seems inclined to look at this bug, here's my proposed fix.
The problem seems to be that ves_icall_System_IO_MonoIO_GetFileSystemEntries()
can return NULL without setting an error.
So I rewrote the code to create an empty string-array in that case.
My code uses the dreaded goto, but
I just used a goto in a patch i submitted tonight too: I enabled the
ability of Win32 to send an idle event message when the app goes idle.
Previously, Win32 mono was not doing that.
Sent on github, if someone wants to review. I tested relevant code on
relevant platforms.
-Rob
On
Awesome, just was hoping it wasn't my end.
-Rob
On Jun 11, 2012, at 11:44 PM, Jonathan Chambers wrote:
Certain warning have been made into errors as the warnings are not safe on
64-bit builds. I am looking into fixing the build now.
Thanks,
Jonathan
On Mon, Jun 11, 2012 at 9:23 PM,
Hey,
I did report that and I also included a (temporary) patch for this (and
possibly other) issue, to make it build successfully.
See one of my previous emails (I cant include a link or attachment right
now as I'm not at home).
Matthias
--
Von: Robert Wilkens
From http://www.mono-project.com/FAQ:_Winforms:
Mono's implementation of WinForms does not support Forms or Controls being
created on multiple threads. All Forms/Controls must be created on the same
thread.
Note this only applies to creation. You can still write multithreaded
applications that
16 matches
Mail list logo
