Re: [go-nuts] Error: opcode not supported on this processor: mips32

To answer this question (after talking on Gopher Slack about this one)… As the target is a 32bit architecture, that max size is max_uint32/4 Sander On 21/08/2017, at 11:32 , Sander van Harmelen wrote: I’ve made some nice progression and am able to generate all kinds of binaries for my mips

Re: [go-nuts] Error: opcode not supported on this processor: mips32

I’ve made some nice progression and am able to generate all kinds of binaries for my mips system now. But I just got a new challenge… When trying to cross compile something that uses pocketsphinx I get this output: GOOS=linux GOARCH=mipsle CGO_ENABLED=1 CC=OpenWrt-Toolchain-ramips-mt7688_gcc-4.

Re: [go-nuts] Error: opcode not supported on this processor: mips32

Thanks for all your help!! Will have a look and play with some options... Sander On 26 Jul 2017, at 03:05, Ian Lance Taylor wrote: > On Sat, Jul 22, 2017 at 12:57 PM, Sander van Harmelen wrote: > > Ok, I managed to get it compiled by first cross compiling libusb and then > pointing to it usi

Re: [go-nuts] Error: opcode not supported on this processor: mips32

On Sat, Jul 22, 2017 at 12:57 PM, Sander van Harmelen wrote: > > Ok, I managed to get it compiled by first cross compiling libusb and then > pointing to it using the linker flags you suggested. So thank you very much, > I can now compile a binary that works on the target device :) > > I do have

Re: [go-nuts] Error: opcode not supported on this processor: mips32

Ok, I managed to get it compiled by first cross compiling libusb and then pointing to it using the linker flags you suggested. So thank you very much, I can now compile a binary that works on the target device :) I do have one additional question… Is it possible to make the resulting binary sta

Re: [go-nuts] Error: opcode not supported on this processor: mips32

Yeah I found suggestions like that. But how does that work then? Does that need to be the lib compiled for the target (mips) or the machine I'm cross compiling on (darwin)? Think I miss some knowledge here :) Sander On 22 Jul 2017, at 19:10, Ian Lance Taylor wrote: > On Sat, Jul 22, 2017 at

Re: [go-nuts] Error: opcode not supported on this processor: mips32

On Sat, Jul 22, 2017 at 4:41 AM, Sander van Harmelen wrote: > Thanks Ian! And sorry for my late response… Didn’t find time the last few > days to test this. I use a different toolchain () and now I seem to get past > this problem :) > > But now I end up getting these errors: > > > /var/folders/2k

Re: [go-nuts] Error: opcode not supported on this processor: mips32

Thanks Ian! And sorry for my late response… Didn’t find time the last few days to test this. I use a different toolchain () and now I seem to get past this problem :) But now I end up getting these errors: /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gou

Re: [go-nuts] Error: opcode not supported on this processor: mips32

On Mon, Jul 17, 2017 at 12:53 PM, Sander van Harmelen wrote: > > I’m trying to cross compile > https://github.com/google/gousb/tree/master/lsusb from macOS to mipsle using > the following cmd: > >> GOOS=linux GOARCH=mipsle CGO_ENABLED=1 CC=mipsel-openwrt-linux-gcc >> CFLAGS=-I../include/ go build

[go-nuts] Error: opcode not supported on this processor: mips32

Hi, I’m trying to cross compile https://github.com/google/gousb/tree/master/lsusb from macOS to mipsle using the following cmd: > GOOS=linux GOARCH=mipsle CGO_ENABLED=1 CC=mipsel-openwrt-linux-gcc > CFLAGS=-I../include/ go build But I receiv