Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Ryan Kirkpatrick]

I am trying to get Mono 2.10 working on a core-image-basic running on 
qemux86 machine. I am using pokay-dylan-9.0.2 on a Debian 6.0.7 system for 
the builds and been able to build and run images without issue. Yet, when 
I went to add the meta-mono layer from git.yoctoporject.org, I started 
running into problems.

I first had to add these lines to the mono_2.10.8.1.bb recipe, and move 
the mono-2.10.8.1/ folder into the files/ folder to get the build to 
succeed. I also added the EXTRA_OECONF line to disable X support (don't 
want winforms, just Mono for console and services).

EXTRA_OECONF += "--without-x --without-moonlight --without-libgdiplus"
FILES_${PN} += "${datadir}/mono-2.0"
FILES_${PN} += "${datadir}/libgc-mono"
INSANE_SKIP_${PN} = "arch dev-so debug-files ldflags"

After that, I built and booted an image with the 'mono' package installed 
and was able to run Mono simply:

$ mono --version
Mono JIT compiler version 2.10.8.1 (tarball Fri Sep 20 14:23:43 MDT 2013)
Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. 
www.mono-project.com
	TLS:           normal
	SIGSEGV:       normal
	Notifications: epoll
	Architecture:  x86
	Disabled:      none
	Misc:          debugger softdebug 
	LLVM:          supported, not enabled.
	GC:            Included Boehm (with typed GC and Parallel Mark)

Yet when I actually tried to run a Mono application (simple console only 
application already compiled on another system), I got this error:

Corlib not in sync with this runtime: expected corlib version 96, found 100.
Loaded from: /usr/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.

It looks like this error indicates some sort mismatch in Mono, as if one 
was mixing between a release and a development version. But there is no 
Mono on my build machine to cause confusion, everything came from the Mono 
recipe. Further, given the issues I encountered above in getting Mono 
built, it appears this recipe has not been tested with more recent version 
of Yocto.

Is there a more current Mono recipe available? Does anyone have any ideas 
on what in this Mono recipe could cause that error? Or do I get to dig in 
and untangle the Mono build? Thanks!

---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------

[meta-mono] Xaramarin no longer providing mono-tools

[Alex J Lennon]

Hi,

I'm about to start testing the meta-mono layer with Yocto on the 
Freescale i.MX6 Sabre board.

I'll feed-back my results testing some simple command line and Windows 
Forms applications
for the readme, assuming this hasn't already been done.

As I setup for this I see that Xamarin are no longer providing 
mono-tools, which is unfortunate
as I can't see a way to develop and debug within Visual Studio, whilst 
targetting a an application
running on Mono/Embedded Linux. Their replacement "Xamarin Studio" seems 
to be targetted
at Android and iOS only.

Is anybody aware of a way to develop/debug on Mono/Yocto with Visual 
Studio with the new
Xamarin plugin?

If not, does anybody happen to have an archived copy of the Mono Tools 
plugin they could
make available to me? (I have a license from Xamarin for this, just need 
the executable)

Many thanks,

Alex Lennon
Director
Dynamic Devices Ltd
http://www.dynamicdevices.co.uk

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Ryan Kirkpatrick]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2127 bytes --]

On Fri, 20 Sep 2013, Ryan Kirkpatrick wrote:

> I am trying to get Mono 2.10 working on a core-image-basic running on 
> qemux86 machine. I am using pokay-dylan-9.0.2 on a Debian 6.0.7 system for 
> the builds and been able to build and run images without issue. Yet, when 
> I went to add the meta-mono layer from git.yoctoporject.org, I started 
> running into problems.
> 
> Corlib not in sync with this runtime: expected corlib version 96, found 100.
> Loaded from: /usr/lib/mono/2.0/mscorlib.dll
> Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.

I dug into the mono build and figured out that I had a version mismatch 
between 'mono' (builds the runtime for the target) and 'mono-native' 
(builds a runtime for the build system and uses it to build the corlib). 
The key was defining both of the following in local.conf, not just the 
first line which is all I had originally.

PREFERRED_VERSION_mono = "2.10.8.1"
PREFERRED_VERSION_mono-native = "2.10.8.1"

Anyway, attached is a patch against meta-mono (from 
git://git.yoctoproject.org/meta-mono) that makes these changes:
 - Adds a comment to the README about the two configs above.
 - Reconfigures mono to be built without X support, skip as desired.
 - A few packaging tweaks, namely moving the bulky *.mdb (Mono debug 
   databases) to the -dbg package.
 - Adjustment to QA packaging checks to resolve errors encountered.
 - Moved the mono-2.10.8.1 folder in meta-mono/recipes/mono to 
   meta-mono/recipes/mono/files so the contents can be found.
 - Quick fix to mono-xsp recipe to avoid parsing error, probably not the 
   fix to make if mono-xsp was going to be built (but I am not).

Hope that helps some one, it does myself as I can now run Mono apps in my 
qemux86 target. Next challenge is to do the same with a qemuarm target 
(actual hardware comes later :)!

---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/x-diff; name=meta-mono-fixes.patch, Size: 8957 bytes --]

Index: meta-mono/README
===================================================================
--- meta-mono/README	(revision 4704)
+++ meta-mono/README	(working copy)
@@ -34,8 +34,17 @@
 Windows Forms applications. While mono can run w/o X, that recipe
 is not supported currently. It is unlikely to be supported.
 
+WARNING:
+If not building the latest version of Mono, make sure that
+PREFERRED_VERSION_* is defined for both mono and mono-native.
+Otherwise the runtime (built by mono recipe) and corlib (built by
+mono-native recipe) will not be in sync! That is, to build Mono
+v2.10.8.1, put this in local.conf or a distro conf:
 
+PREFERRED_VERSION_mono = "2.10.8.1"
+PREFERRED_VERSION_mono-native = "2.10.8.1"
 
+
 3) Maintainer(s) & Patch policy
 
 Autif Khan (autif.mlist@gmail.com)
Index: meta-mono/recipes-mono/mono/mono_2.10.8.1.bb
===================================================================
--- meta-mono/recipes-mono/mono/mono_2.10.8.1.bb	(revision 4704)
+++ meta-mono/recipes-mono/mono/mono_2.10.8.1.bb	(working copy)
@@ -2,11 +2,12 @@
 
 inherit autotools pkgconfig
 
-DEPENDS =+ "mono-native libgdiplus"
+DEPENDS =+ "mono-native"
 
-PR = "r0"
+PR = "r1"
 
 EXTRA_OECONF += "--disable-mcs-build mono_cv_uscore=no --with-tls=pthread --with-sigaltstack=no --with-mcs-docs=no"
+EXTRA_OECONF += "--without-x --without-moonlight --without-libgdiplus"
 
 do_configure_prepend() {
 	autoreconf -Wcross --verbose --install --force || bbnote "mono failed to autoreconf"
@@ -25,6 +26,9 @@
 FILES_${PN} += "${libdir}/libikvm-native.so"
 FILES_${PN} += "${libdir}/libMonoPosixHelper.so"
 FILES_${PN} += "${libdir}/libMonoSupportW.so"
+FILES_${PN} += "${datadir}/mono-2.0"
+FILES_${PN} += "${datadir}/libgc-mono"
+FILES_${PN}-dbg += "usr/lib/mono/*/*.mdb usr/lib/mono/*/*/*.mdb usr/lib/mono/*/*/*/*.mdb"
 
-INSANE_SKIP_${PN} = "arch dev-so debug-files"
+INSANE_SKIP_${PN} = "arch dev-so debug-files ldflags"
 
Index: meta-mono/recipes-mono/mono/files/mono-2.10.8.1/Makefile.am.diff
===================================================================
--- meta-mono/recipes-mono/mono/files/mono-2.10.8.1/Makefile.am.diff	(revision 0)
+++ meta-mono/recipes-mono/mono/files/mono-2.10.8.1/Makefile.am.diff	(revision 4765)
@@ -0,0 +1,15 @@
+--- mono-2.10.8.1.orig/Makefile.am	2012-01-25 14:24:43.564002232 -0500
++++ mono-2.10.8.1/Makefile.am	2012-01-25 14:25:02.036002218 -0500
+@@ -4,10 +4,10 @@
+ MOONLIGHT_SUBDIRS = $(libgc_dir) eglib/src mono
+ 
+ if CROSS_COMPILING
+-SUBDIRS = po $(libgc_dir) eglib mono $(ikvm_native_dir) data runtime scripts man samples msvc $(docs_dir)
++SUBDIRS = po $(libgc_dir) eglib mono $(ikvm_native_dir) support data runtime scripts man samples msvc $(docs_dir)
+ # Keep in sync with SUBDIRS
+ ## 'tools' is not normally built
+-DIST_SUBDIRS = po libgc eglib mono ikvm-native         data runtime scripts man samples tools msvc docs
++DIST_SUBDIRS = po libgc eglib mono ikvm-native support data runtime scripts man samples tools msvc docs
+ else
+ if ONLY_MOONLIGHT
+ SUBDIRS = $(MOONLIGHT_SUBDIRS) runtime
Index: meta-mono/recipes-mono/mono/files/mono-2.10.8.1/mcs/class/Makefile.diff
===================================================================
--- meta-mono/recipes-mono/mono/files/mono-2.10.8.1/mcs/class/Makefile.diff	(revision 0)
+++ meta-mono/recipes-mono/mono/files/mono-2.10.8.1/mcs/class/Makefile.diff	(revision 4765)
@@ -0,0 +1,13 @@
+--- mono-2.10.8.1.orig/mcs/class/Makefile	2012-01-27 16:20:36.319297999 -0500
++++ mono-2.10.8.1/mcs/class/Makefile	2012-01-27 20:37:30.867593825 -0500
+@@ -55,10 +55,8 @@
+ 	Novell.Directory.Ldap		\
+ 	Mono.Security.Win32		\
+ 	System.DirectoryServices	\
+-	RabbitMQ.Client			\
+ 	Mono.Messaging			\
+ 	System.Messaging	        \
+-	Mono.Messaging.RabbitMQ		\
+ 	System.ServiceProcess           \
+ 	System.Drawing.Design		\
+ 	System.Design			\
Index: meta-mono/recipes-mono/mono/files/mono-2.10.8.1/data/config.in.diff
===================================================================
--- meta-mono/recipes-mono/mono/files/mono-2.10.8.1/data/config.in.diff	(revision 0)
+++ meta-mono/recipes-mono/mono/files/mono-2.10.8.1/data/config.in.diff	(revision 4765)
@@ -0,0 +1,11 @@
+--- mono-2.10.8.1.orig/data/config.in	2012-01-27 09:29:07.072001924 -0500
++++ mono-2.10.8.1/data/config.in	2012-01-27 09:30:59.740001933 -0500
+@@ -15,7 +15,7 @@
+ 	<dllmap dll="i:msvcrt.dll" target="@LIBC@" os="!windows"/>
+ 	<dllmap dll="sqlite" target="@SQLITE@" os="!windows"/>
+ 	<dllmap dll="sqlite3" target="@SQLITE3@" os="!windows"/>
+-	<dllmap dll="libX11" target="@X11@" os="!windows" />
++	<dllmap dll="libX11" target="libX11.so.6" os="!windows" />
+ 	<dllmap dll="libcairo-2.dll" target="libcairo.so.2" os="!windows"/>
+ 	<dllmap dll="libcairo-2.dll" target="libcairo.2.dylib" os="osx"/>
+ 	<dllmap dll="libcups" target="libcups.so.2" os="!windows"/>
Index: meta-mono/recipes-mono/mono/mono-native_2.10.8.1.bb
===================================================================
--- meta-mono/recipes-mono/mono/mono-native_2.10.8.1.bb	(revision 4704)
+++ meta-mono/recipes-mono/mono/mono-native_2.10.8.1.bb	(working copy)
@@ -5,6 +5,7 @@
 PR = "r1"
 
 EXTRA_OECONF += "mono_cv_uscore=no --with-tls=pthread --with-sigaltstack=no --with-mcs-docs=no"
+EXTRA_OECONF += "--without-x --without-moonlight --without-libgdiplus"
 
 do_configure_prepend() {
     autoreconf -Wcross --verbose --install --force || bbnote "mono-native failed to autoreconf"
Index: meta-mono/recipes-mono/mono/mono-2.10.8.1/data/config.in.diff
===================================================================
--- meta-mono/recipes-mono/mono/mono-2.10.8.1/data/config.in.diff	(revision 4704)
+++ meta-mono/recipes-mono/mono/mono-2.10.8.1/data/config.in.diff	(working copy)
@@ -1,11 +0,0 @@
---- mono-2.10.8.1.orig/data/config.in	2012-01-27 09:29:07.072001924 -0500
-+++ mono-2.10.8.1/data/config.in	2012-01-27 09:30:59.740001933 -0500
-@@ -15,7 +15,7 @@
- 	<dllmap dll="i:msvcrt.dll" target="@LIBC@" os="!windows"/>
- 	<dllmap dll="sqlite" target="@SQLITE@" os="!windows"/>
- 	<dllmap dll="sqlite3" target="@SQLITE3@" os="!windows"/>
--	<dllmap dll="libX11" target="@X11@" os="!windows" />
-+	<dllmap dll="libX11" target="libX11.so.6" os="!windows" />
- 	<dllmap dll="libcairo-2.dll" target="libcairo.so.2" os="!windows"/>
- 	<dllmap dll="libcairo-2.dll" target="libcairo.2.dylib" os="osx"/>
- 	<dllmap dll="libcups" target="libcups.so.2" os="!windows"/>
Index: meta-mono/recipes-mono/mono/mono-2.10.8.1/Makefile.am.diff
===================================================================
--- meta-mono/recipes-mono/mono/mono-2.10.8.1/Makefile.am.diff	(revision 4704)
+++ meta-mono/recipes-mono/mono/mono-2.10.8.1/Makefile.am.diff	(working copy)
@@ -1,15 +0,0 @@
---- mono-2.10.8.1.orig/Makefile.am	2012-01-25 14:24:43.564002232 -0500
-+++ mono-2.10.8.1/Makefile.am	2012-01-25 14:25:02.036002218 -0500
-@@ -4,10 +4,10 @@
- MOONLIGHT_SUBDIRS = $(libgc_dir) eglib/src mono
- 
- if CROSS_COMPILING
--SUBDIRS = po $(libgc_dir) eglib mono $(ikvm_native_dir) data runtime scripts man samples msvc $(docs_dir)
-+SUBDIRS = po $(libgc_dir) eglib mono $(ikvm_native_dir) support data runtime scripts man samples msvc $(docs_dir)
- # Keep in sync with SUBDIRS
- ## 'tools' is not normally built
--DIST_SUBDIRS = po libgc eglib mono ikvm-native         data runtime scripts man samples tools msvc docs
-+DIST_SUBDIRS = po libgc eglib mono ikvm-native support data runtime scripts man samples tools msvc docs
- else
- if ONLY_MOONLIGHT
- SUBDIRS = $(MOONLIGHT_SUBDIRS) runtime
Index: meta-mono/recipes-mono/mono/mono-2.10.8.1/mcs/class/Makefile.diff
===================================================================
--- meta-mono/recipes-mono/mono/mono-2.10.8.1/mcs/class/Makefile.diff	(revision 4704)
+++ meta-mono/recipes-mono/mono/mono-2.10.8.1/mcs/class/Makefile.diff	(working copy)
@@ -1,13 +0,0 @@
---- mono-2.10.8.1.orig/mcs/class/Makefile	2012-01-27 16:20:36.319297999 -0500
-+++ mono-2.10.8.1/mcs/class/Makefile	2012-01-27 20:37:30.867593825 -0500
-@@ -55,10 +55,8 @@
- 	Novell.Directory.Ldap		\
- 	Mono.Security.Win32		\
- 	System.DirectoryServices	\
--	RabbitMQ.Client			\
- 	Mono.Messaging			\
- 	System.Messaging	        \
--	Mono.Messaging.RabbitMQ		\
- 	System.ServiceProcess           \
- 	System.Drawing.Design		\
- 	System.Design			\
Index: meta-mono/recipes-mono/mono-xsp/mono-xsp_1.2.5.bb
===================================================================
--- meta-mono/recipes-mono/mono-xsp/mono-xsp_1.2.5.bb	(revision 4704)
+++ meta-mono/recipes-mono/mono-xsp/mono-xsp_1.2.5.bb	(working copy)
@@ -91,7 +91,7 @@
 	/usr/lib/mono/2.0/mod-mono-server2.exe \
 	/usr/bin/mod-mono-server2 \
 	"
-FILES_mono-xsp-dev = "\
+FILES_mono-xsp2-dev = "\
 	/usr/lib/pkgconfig/xsp.pc \
 	/usr/lib/pkgconfig/xsp-2.pc \
 	"

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Paul Eggleton]

Hi Ryan,

On Thursday 26 September 2013 18:04:03 Ryan Kirkpatrick wrote:
> On Fri, 20 Sep 2013, Ryan Kirkpatrick wrote:
> > I am trying to get Mono 2.10 working on a core-image-basic running on
> > qemux86 machine. I am using pokay-dylan-9.0.2 on a Debian 6.0.7 system for
> > the builds and been able to build and run images without issue. Yet, when
> > I went to add the meta-mono layer from git.yoctoporject.org, I started
> > running into problems.
> > 
> > Corlib not in sync with this runtime: expected corlib version 96, found
> > 100. Loaded from: /usr/lib/mono/2.0/mscorlib.dll
> > Download a newer corlib or a newer runtime at
> > http://www.go-mono.com/daily.
> 
> I dug into the mono build and figured out that I had a version mismatch
> between 'mono' (builds the runtime for the target) and 'mono-native'
> (builds a runtime for the build system and uses it to build the corlib).
> The key was defining both of the following in local.conf, not just the
> first line which is all I had originally.
> 
> PREFERRED_VERSION_mono = "2.10.8.1"
> PREFERRED_VERSION_mono-native = "2.10.8.1"
> 
> Anyway, attached is a patch against meta-mono (from
> git://git.yoctoproject.org/meta-mono) that makes these changes:
>  - Adds a comment to the README about the two configs above.
>  - Reconfigures mono to be built without X support, skip as desired.
>  - A few packaging tweaks, namely moving the bulky *.mdb (Mono debug
>    databases) to the -dbg package.
>  - Adjustment to QA packaging checks to resolve errors encountered.
>  - Moved the mono-2.10.8.1 folder in meta-mono/recipes/mono to
>    meta-mono/recipes/mono/files so the contents can be found.
>  - Quick fix to mono-xsp recipe to avoid parsing error, probably not the
>    fix to make if mono-xsp was going to be built (but I am not).
> 
> Hope that helps some one, it does myself as I can now run Mono apps in my
> qemux86 target. Next challenge is to do the same with a qemuarm target
> (actual hardware comes later :)!

Have you sent these fixes to the layer maintainer - Autif Khan 
(autif.mlist@gmail.com) ? It would be good to get those integrated.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Ryan Kirkpatrick]

On Tue, 8 Oct 2013, Paul Eggleton wrote:

> Have you sent these fixes to the layer maintainer - Autif Khan 
> (autif.mlist@gmail.com) ? It would be good to get those integrated.

Yes, I did shortly after my post to the list, but I have not heard any 
response. 

Since then I have run into some issues with Mono v2.10 itself and my 
company's existing (proprietary) code base. It is an odd issue around 
events and a complex class hierarchy that I had encountered in the past 
with Mono v2.4 (but not v2.2). I traced it down to a single change in Mono 
and backed out that change for the previous product (an embedded server). 
I did report it to the Mono list at that time, but there was no simple 
test case I could share.

Anyway, I did a quick test with Mono v3.2 (from their web site on OS X) 
and the issues were no longer present. Hence, for the new product that I 
plan to use Yocto to develop, I am going to use Mono v3.2. Of course the 
current Mono layer has a lot more than we need (which is only the runtime 
and corelib, no X, xsp, etc...) but only includes support through v2.11. I 
am currently considering whether updating the existing meta-mono layer for 
v3.2 or just writing a quick recipe for just want we need from Mono.

This is complicated by a quick attempt to build the existing Mono layer 
for ARM failing. The failure was on the ARM objcopy not knowing what to do 
with mcs.exe.so as it is .NET assembly wrapped as an i386 shared object. 
This was during the generation of the debug package files, so looks like 
that process needs to be tweaked to understand this special case. 

I would welcome any advice on how to proceed with Mono v3.2 recipes and 
for building on ARM. Thanks!

---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Alex J Lennon]

[-- Attachment #1: Type: text/plain, Size: 3776 bytes --]


On 09/10/2013 20:52, Ryan Kirkpatrick wrote:
> On Tue, 8 Oct 2013, Paul Eggleton wrote:
>
>> Have you sent these fixes to the layer maintainer - Autif Khan
>> (autif.mlist@gmail.com) ? It would be good to get those integrated.
> Yes, I did shortly after my post to the list, but I have not heard any
> response.
>
> Since then I have run into some issues with Mono v2.10 itself and my
> company's existing (proprietary) code base. It is an odd issue around
> events and a complex class hierarchy that I had encountered in the past
> with Mono v2.4 (but not v2.2). I traced it down to a single change in Mono
> and backed out that change for the previous product (an embedded server).
> I did report it to the Mono list at that time, but there was no simple
> test case I could share.
>
> Anyway, I did a quick test with Mono v3.2 (from their web site on OS X)
> and the issues were no longer present. Hence, for the new product that I
> plan to use Yocto to develop, I am going to use Mono v3.2. Of course the
> current Mono layer has a lot more than we need (which is only the runtime
> and corelib, no X, xsp, etc...) but only includes support through v2.11. I
> am currently considering whether updating the existing meta-mono layer for
> v3.2 or just writing a quick recipe for just want we need from Mono.
>
> This is complicated by a quick attempt to build the existing Mono layer
> for ARM failing. The failure was on the ARM objcopy not knowing what to do
> with mcs.exe.so as it is .NET assembly wrapped as an i386 shared object.
> This was during the generation of the debug package files, so looks like
> that process needs to be tweaked to understand this special case.

Hi Ryan - I've built Mono out of meta-mono for a couple of different 
targets in the past
and am revisiting now for a mesh edge gateway we're working on here.

I see that Mono no longer seems to be building against Yocto head / 
qemux86 (for me
at least) and am considering looking at a recipe to build the current 
release of Mono
whilst I dig into why this is.

I wondered if you'd made any progress with this at all in the past few 
weeks?

Thanks / Best Regards,

Alex

> I would welcome any advice on how to proceed with Mono v3.2 recipes and
> for building on ARM. Thanks!
>
> ---------------------------------------------------------------------------
> | Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
> ---------------------------------------------------------------------------
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

-- 

Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

Linkedin <http://www.linkedin.com/in/alexjlennon> Skype 
<skype:alexjlennon?add>

This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended 
recipient(s). Any unauthorized disclosure, dissemination, distribution, 
copying or the taking of any action in reliance on the information 
herein is prohibited. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, or contain viruses. 
Anyone who communicates with us by e-mail is deemed to have accepted 
these risks. Company Name is not responsible for errors or omissions in 
this message and denies any responsibility for any damage arising from 
the use of e-mail. Any opinion and other statement contained in this 
message and any attachment are solely those of the author and do not 
necessarily represent those of the company.


[-- Attachment #2.1: Type: text/html, Size: 6546 bytes --]

[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]

[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]

[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Ryan Kirkpatrick]

On Thu, 31 Oct 2013, Alex J Lennon wrote:

> I see that Mono no longer seems to be building against Yocto head / 
> qemux86 (for me at least) and am considering looking at a recipe to 
> build the current release of Mono whilst I dig into why this is.
> 
> I wondered if you'd made any progress with this at all in the past few 
> weeks?

Unfortunately I have not made any progress and probably will not for a 
while. Before I could get started on recipes, priorities on the project 
that the Mono build was for got shifted around and I have spent the past 
month on other tasks. I might be able to get back to it before the end of 
the year, but I will not mind if you beat me to it. :)

Let me know if you make any progress! Thanks! 

---------------------------------------------------------------------------
| "For to me to live is Christ, and to die is gain." --- Phil. 1:21 (KJV) |
---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------

Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

[Alex J Lennon]

[-- Attachment #1: Type: text/plain, Size: 2714 bytes --]


On 02/11/2013 21:49, Ryan Kirkpatrick wrote:
> On Thu, 31 Oct 2013, Alex J Lennon wrote:
>
>> I see that Mono no longer seems to be building against Yocto head /
>> qemux86 (for me at least) and am considering looking at a recipe to
>> build the current release of Mono whilst I dig into why this is.
>>
>> I wondered if you'd made any progress with this at all in the past few
>> weeks?
> Unfortunately I have not made any progress and probably will not for a
> while. Before I could get started on recipes, priorities on the project
> that the Mono build was for got shifted around and I have spent the past
> month on other tasks. I might be able to get back to it before the end of
> the year, but I will not mind if you beat me to it. :)
>
> Let me know if you make any progress! Thanks!

I have been working on this and have Mono 3.2.3 building for qemux86. 
I've successfully
tested it with both a simple console and Windows Forms "Hello World" 
application within
qemu.

I'm working on running this against an i.MX6 machine, imx6qsabresd, out
of meta-fsl-arm but it is currently failing on something related to the 
libgdiplus support.

I'll provide an update when I have it going.

Cheers,

Alex

> ---------------------------------------------------------------------------
> | "For to me to live is Christ, and to die is gain." --- Phil. 1:21 (KJV) |
> ---------------------------------------------------------------------------
> | Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
> ---------------------------------------------------------------------------
>
>

-- 

Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

Linkedin <http://www.linkedin.com/in/alexjlennon> Skype 
<skype:alexjlennon?add>

This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended 
recipient(s). Any unauthorized disclosure, dissemination, distribution, 
copying or the taking of any action in reliance on the information 
herein is prohibited. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, or contain viruses. 
Anyone who communicates with us by e-mail is deemed to have accepted 
these risks. Company Name is not responsible for errors or omissions in 
this message and denies any responsibility for any damage arising from 
the use of e-mail. Any opinion and other statement contained in this 
message and any attachment are solely those of the author and do not 
necessarily represent those of the company.


[-- Attachment #2.1: Type: text/html, Size: 5234 bytes --]

[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]

[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]

[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]