Interesting idea, but has the Go team expressed interest in creating such a
tool?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googleg
>
> 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
go is a trivial
"Hello, world!" program.)
On the target (mips) device, I see files like /lib/libuClibc-0.9.33.2.so,
with /lib/libc.so.0 being a symlink to /lib/libuClibc-0.9.33.2.so, in case
that's relevant.
Thanks!
--Steve
On Friday, February 10, 2017 at 7:58:58 PM UTC-8, S
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,
> 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
