From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: linux@rkirkpat.net
Cc: yocto@yoctoproject.org, paul.eggleton@linux.intel.com
Subject: Re: Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...
Date: Thu, 31 Oct 2013 16:44:34 +0000 [thread overview]
Message-ID: <527288F2.70607@dynamicdevices.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1310091328540.27991@magellan.rkirkpat.net>
[-- 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 --]
next prev parent reply other threads:[~2013-10-31 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 23:44 Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime Ryan Kirkpatrick
2013-09-21 8:31 ` [meta-mono] Xaramarin no longer providing mono-tools Alex J Lennon
2013-09-27 0:04 ` Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime Ryan Kirkpatrick
2013-10-08 17:30 ` Paul Eggleton
2013-10-09 19:52 ` Ryan Kirkpatrick
2013-10-31 16:44 ` Alex J Lennon [this message]
2013-11-02 21:49 ` Ryan Kirkpatrick
2013-11-03 13:46 ` Alex J Lennon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527288F2.70607@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=linux@rkirkpat.net \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.