[Mono-dev] Building from Source Fails with mcs: Command not found (Mono-devel-list Digest, Vol 121, Issue 19)

[cyd]

This may sound like an obvious question but shouldn't the 'make test' that I
ran in mono/mono...after running 'make clean && make' in mono/mono pick that
up?  Should I be running 'make tests' in mono/mini/mono instead?


Jo Shields wrote
> On 21/05/15 12:39, cyd wrote:
>> Done.  Results were:
>>
>> make[3]: Entering directory `/bld/mono/mono-4.0.0/mono/mini'
>> MONO_PATH=/bld/mono/mono-4.0.0/mcs/class/lib/net_4_5
>> ../../runtime/mono-wrapper
>> /bld/mono/mono-4.0.0/mcs/class/lib/build/mcs.exe
>> -unsafe -nowarn:0162 -out:TestDriver.dll -target:library TestDriver.cs
>> Illegal instruction
> 
> basic.exe is *supposed* to be "PE32 executable for MS Windows (console)
> Intel 80386 32-bit Mono/.Net assembly" - all .NET apps are.
> 
> You're missing the most important part here: the "Illegal instruction".
> 
> SIGILL comes from the kernel when your Mono runtime (mono/mini/mono) is
> trying to execute instructions which your CPU doesn't support - e.g.
> ARMv7 instructions on an ARMv6 chip.
> 
> This error here means your compiled Mono runtime in mono/mini is trying
> to execute basic.exe, issuing a CPU instruction which your CPU doesn't
> have, and crashing.
> _______________________________________________
> Mono-devel-list mailing list

> Mono-devel-list at .ximian

> http://lists.ximian.com/mailman/listinfo/mono-devel-list





--
View this message in context: http://mono.1490590.n4.nabble.com/Building-from-Source-Fails-with-mcs-Command-not-found-tp4666000p4666018.html
Sent from the Mono - Dev mailing list archive at Nabble.com.