>
> Do you need gccgo, cgo or cross compiling?
>
Cross-compiling. I'm trying to cross-compile Go programs from an x86_64
Linux machine to run on a MIPS (32-bit) target machine with no software and
no hardware FPU.
Without FPU however you will get "illegal instruction" when running the
> bin
Do you need gccgo, cgo or cross compiling?
I don't know about that, but otherwise the default compiler should work for
mipsle (32 bit little endian) "since" go 1.8.
Without FPU however you will get "illegal instruction" when running the
binary.
There are 2 possibilities:
Wait for vstefanovic t
Progress:
I assumed that I could use so I jumped
to https://github.com/golang/go/wiki/GccgoCrossCompilation#symlink and
followed those instructions. I then compiled with gcc, gccgo, and ar all
symlinked to a place in my $PATH that occurs before the non-mips gcc etc
programs.
After compiling
I should add that my target device's kernel doesn't have FPU (floating
point) emulation, nor does it have a hardware FPU, and I therefore can't
just use go1.8r3's easy-to-use mips support; already tried it.
--Steve
On Friday, February 10, 2017 at 7:56:40 PM UTC-8, Steve Phillips wrote:
>
> > Y
> Yes, crosscompiling to mips with gccgo has worked for a while.
I'm having trouble getting this to work. I got gccgo-mips-linux-gnu to
produce binaries, but the target machine doesn't have the right shared
libraries to run them; I get *"can't load library 'libm.so.6'"* when trying
to execute
