fwiw. You will likely need to ensure that your build of 'mono-native'
and 'mono' recipes are both in sync.
That solved the issue!
Thanks!
Daniel
Alex J Lennon ajlen...@dynamicdevices.co.uk schrieb am Di., 28. Juli 2015
um 19:08 Uhr:
On 28/07/2015 17:59, Zoltan Varga wrote:
Hi,
It
On 29/07/2015 08:43, Daniel Kuhne wrote:
fwiw. You will likely need to ensure that your build of 'mono-native'
and 'mono' recipes are both in sync.
That solved the issue!
Great! Thanks for letting me know. You prompted me to look at the git
support last night as I've been concentrating on
Hello,
I am getting assertion:
* Assertion at class.c:5078, condition `class' not met
Native stacktrace:
mono() [0x48f940]
=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono
yes, produce a minimal test case that exhibits the issue.
On Tue, Jul 28, 2015 at 3:24 AM, Daniel Kuhne dakui...@gmail.com wrote:
Hello,
I am getting assertion:
* Assertion at class.c:5078, condition `class' not met
Native stacktrace:
mono() [0x48f940]
Hi,
It is a transient failure when using a mismatching mono runtime and
mscorlib.dll. Make sure you are using the latest version of both.
Zoltan
On Tue, Jul 28, 2015 at 12:22 PM, Daniel Kuhne dakui...@gmail.com wrote:
I test with a simple VB.NET Hello World console
On 28/07/2015 17:59, Zoltan Varga wrote:
Hi,
It is a transient failure when using a mismatching mono runtime and
mscorlib.dll. Make sure you are using the latest version of both.
Zoltan
fwiw. You will likely need to ensure that your build of 'mono-native'
and 'mono' recipes
I test with a simple VB.NET Hello World console application. Just doing
System.Console.WriteLine().
I build with yocto using meta-mono where I am using for mono:
c65aec96e46692ae68df34cf0849c8ff6871507e from master branch (git://
github.com/mono/mono.git)
and mono-basic 4.0
Using origninal mono
