[Mono-dev] Mono 2.6.1, Moonlight 2.0, ARM5

Rafael Teixeira monoman at gmail.com
Thu Feb 4 10:25:53 EST 2010

AFAIK, Moonlight really wasn't configured to support other archs,
besides x86/x64.

Can't look into that just but I think that it really looks like that
some needed moonlight lib function isn't being built for your
environment, as perhaps it depends on some header file that may be
missing on ARM.

Please see the config.log to see what was turned down for your
environment, it is easier than trying to follow the chain of
dependencies in the autoconf files.

Go ahead: I would love to see Moonlight running on the Android and
some other hardware that sports ARM cpus.

Hope it helps,

Rafael "Monoman" Teixeira
"To be creative means to be in love with life. You can be creative
only if you love life enough that you want to enhance its beauty, you
want to bring a little more music to it, a little more poetry to it, a
little more dance to it."

On Thu, Feb 4, 2010 at 11:33 AM, technomage1972
<dellis1972 at googlemail.com> wrote:
> Hi
> I recently found a problem trying to run Moonlight on an ARM5 based
> platform.
> The full details are  http://old.nabble.com/Moonlight-on-ARM-td27255440.html
> here .
> Basically , after building and installing mono 2.6.1 and moonlight 2.0
> running mopen simpleclock from the command line, the following is produced.
> **
> ** ERROR:(mini-arm.c:2663):arm_patch_general: code should not be reached
> Stacktrace:
>  at Mono.NativeDependencyObjectHelper.Lookup (Mono.Kind,intptr)
> <0xffffffff>
>  at Mono.NativeDependencyObjectHelper.Lookup (Mono.Kind,intptr) <0x000e8>
>  at System.Windows.Deployment.get_Current () <0x0001b>
>  at System.Windows.DependencyProperty.LookupInternal
> (Mono.Kind,string,System.Type,bool) <0x00057>
>  at System.Windows.DependencyProperty.Lookup (Mono.Kind,string,System.Type)
> <0x0002f>
>  at System.Windows.Deployment..cctor () <0x00037>
>  at (wrapper runtime-invoke) object.runtime_invoke_void
> (object,intptr,intptr,intptr) <0x0006b>
>  at Moonlight.Gtk.MoonlightHost.LoadXap (string) <0xffffffff>
>  at Moonlight.Gtk.MoonlightHost.LoadXap (string) <0x00028>
>  at MonoOpen.LoadXap (string,System.Collections.Generic.List`1<string>)
> <0x0037f>
>  at MonoOpen.DoLoad (string,System.Collections.Generic.List`1<string>)
> <0x000a7>
>  at MonoOpen.Main (string[]) <0x00d1f>
>  at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object
> (object,intptr,intptr,intptr) <0x00073>
> I have tried to look into the code to find out what the issue is, but it
> gets a bit confusing once you get into the native calls. Both normal mono
> and winforms apps work correctly btw, this just affects moonlight. My Gut
> feeling is that the moon native library is not being compiled with the
> correct flags, having looked at the moonlight configure script there are
> very few references to ARM in it (unlike the mono configure script).
> I did submit a but report
> https://bugzilla.novell.com/show_bug.cgi?id=573975 here  but I'm sure there
> are more important things for the Mono dev's to work on.
> I'm quite happy to try to fix this issue myself  and post a patch (I have
> the hardware) but I need some pointers to get started. So does anyone has
> any suggestions?
> Dean
> --
> View this message in context: http://old.nabble.com/Mono-2.6.1%2C-Moonlight-2.0%2C-ARM5-tp27452189p27452189.html
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list