[Mono-dev] Mono 2.2 and OpenEmbedded
I am trying to compile Mono with OpenEmbedded. I have sucessfully compiled the 1.2.6 version. And when I'm trying to compile the mono-1.9.1+2.2-rc1 version, I obtain this error : Invalid opcode addps at line 412 make[3]: *** [cpu-x86.h] Error 9 make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/mini' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2' make: *** [all] Error 2 FATAL: oe_runmake failed I would gladly accept any help you could provide since I'm completly clueless about the origin of this error nor about about a way to correct it. Thanks, Paul. Following, the complete log : NOTE: make -j 4 make all-recursive make[1]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2' Making all in po make[2]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po' Making all in mcs make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po/mcs' make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po/mcs' make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po' make[2]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/po' Making all in libgc make[2]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc' Making all in include make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include' Making all in private make[4]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include/private' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include/private' make[4]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include' make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/include' Making all in doc make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/doc' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc/doc' make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc' make[2]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/libgc' Making all in mono make[2]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono' Making all in utils make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/utils' make all-am make[4]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/utils' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/utils' make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/utils' Making all in io-layer make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/io-layer' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/io-layer' Making all in os make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/os' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/os' Making all in cil make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/cil' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/cil' Making all in metadata make[3]: Entering directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/metadata' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/metadata' Making all i
Re: [Mono-dev] Mono 2.2 and OpenEmbedded
On Mon, Jun 22, 2009 at 2:18 PM, wrote: > I am trying to compile Mono with OpenEmbedded. > I have sucessfully compiled the 1.2.6 version. > And when I'm trying to compile the mono-1.9.1+2.2-rc1 version, I > obtain this error : > > Invalid opcode addps at line 412 > make[3]: *** [cpu-x86.h] Error 9 > make[3]: Leaving directory > > `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono/mini' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2/mono' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/opt/oe/build/tmp/work/i686-oe-linux/mono-1.9.1+2.2-rc1-r3/mono-2.2' > make: *** [all] Error 2 > FATAL: oe_runmake failed > What on earth is "1.9.1+2.2-rc1-r3"? Any reason on why not use mono 2.4 which is the latest stable version? Cheers, Rodrigo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 2.2 and OpenEmbedded
> What on earth is "1.9.1+2.2-rc1-r3"? Any reason on why not use mono 2.4 > which is the > latest stable version? > > Cheers, > Rodrigo > Compiling with Bitbake requires Bitbake (.bb) files. OpenEmbedded provides recipes of the mono-1.2.6 version which compiled correctly and this 1.9.1+2.2 version which is, I suppose, a combined file for the 1.9.1 and the 2.2 version. Since I'm a novice, I'm trying to compile the already provided versions before creating myself a .bb file. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 2.2 and OpenEmbedded
On Tue, Jun 23, 2009 at 5:12 AM, wrote: > > What on earth is "1.9.1+2.2-rc1-r3"? Any reason on why not use mono 2.4 >> which is the >> latest stable version? >> >> Cheers, >> Rodrigo >> >> > Compiling with Bitbake requires Bitbake (.bb) files. OpenEmbedded provides > recipes of the mono-1.2.6 version which compiled correctly and this > 1.9.1+2.2 version which is, I suppose, a combined file for the 1.9.1 and the > 2.2 version. Since I'm a novice, I'm trying to compile the already provided > versions before creating myself a .bb file. > > You'll have to ask the OE community for help on the 1.9.1+2.2 frankenstein as this is not a configuration seen outside. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
