[Mono-dev] MIPS64 port status
Zoltan Varga
vargaz at gmail.com
Wed Jul 16 00:04:10 UTC 2014
Hi,
mips32 support used to work a few years ago, i.e. it could run a full
bootstrap and a large portion of the mono test suite. It might be somewhat
broken now but it could probably be fixed with a small amount of work.
Doing a new port, even a 32->64 bit port is a large amount of work.
Zoltan
On Wed, Jul 16, 2014 at 1:28 AM, Jose A. Saumell <saumell.jose at gmail.com>
wrote:
> Hello!
>
> I have the task to port mono runtime to an Octeon MIPS64 based platform
> running OpenWrt.
>
> I have tried to cross-compile but eventually run into an error:
> ////
> ake[7]: Entering directory
> `/home/jose/erl/openwrt/build_dir/target-mips64_octeon_64_eglibc-2.19/mono-3.0.10/mono/utils'
> ../../doltcompile mips64-openwrt-linux-gnu-gcc -DHAVE_CONFIG_H -I.
> -I../.. -I../.. -I../../mono -I../../libgc/include -I../../eglib/src
> -I../../eglib/src
> -I/home/jose/erl/openwrt/staging_dir/target-mips64_octeon_64_eglibc-2.19/usr/include
> -I/home/jose/erl/openwrt/staging_dir/target-mips64_octeon_64_eglibc-2.19/include
> -I/home/jose/erl/openwrt/staging_dir/toolchain-mips64_octeon_64_gcc-4.6-linaro_eglibc-2.19/usr/include
> -I/home/jose/erl/openwrt/staging_dir/toolchain-mips64_octeon_64_gcc-4.6-linaro_eglibc-2.19/include
> -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP
> -D__default_codegen__ -DUSE_COMPILER_TLS -DNO_UNALIGNED_ACCESS -Os -pipe
> -mno-branch-likely -march=octeon -mabi=64 -fno-caller-saves -fhonour-copts
> -Wno-error=unused-but-set-variable -msoft-float -Wformat
> -Werror=format-security -fno-strict-aliasing -Wdeclaration-after-statement
> -Wno-unused-but-set-variable -g -Wall -Wunused -Wmissing-prototypes
> -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes
> -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wwrite-strings -Wno-switch
> -Wno-switch-enum -Wno-unused-value -Werror-implicit-function-declaration
> -MT mono-io-portability.lo -MD -MP -MF .deps/mono-io-portability.Tpo -c -o
> mono-io-portability.lo mono-io-portability.c
> In file included from ../../mono/utils/mono-stack-unwinding.h:10:0,
> from ../../mono/metadata/object-internals.h:13,
> from ../../mono/metadata/gc-internal.h:14,
> from mono-io-portability.c:13:
> ../../mono/utils/mono-context.h:470:2: error: #error "Implement
> mono-context for the current arch"
> In file included from ../../mono/utils/mono-stack-unwinding.h:10:0,
> from ../../mono/metadata/object-internals.h:13,
> from ../../mono/metadata/gc-internal.h:14,
> from mono-io-portability.c:13:
> ../../mono/utils/mono-context.h:474:44: error: unknown type name
> 'MonoContext'
> ////
>
>
> Before I dig any further I wanted to consult the developer community on
> mips64 port status and any other relevant information you could provide to
> move forward with this task.
>
> I appreciate your help,
>
> Regards, Jose
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140716/d060c35c/attachment-0001.html>
More information about the Mono-devel-list
mailing list