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 <san...@xanzy.io> wrote: I’ve made some nice progression and am able to generate all

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

:1248: type [2147483647]uint32 too large Is there a compile option I need to use to fix this? Or is the problem in the types used by pocketsphinx.go in conjunction with my target architecture? Sander On 26/07/2017, at 07:23 , Sander van Harmelen <san...@xanzy.io> wrote: Thanks for all you

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 <i...@golang.org> wrote: > On Sat, Jul 22, 2017 at 12:57 PM, Sander van Harmelen <san...@xanzy.io> wrote: > > Ok, I managed to get it compiled by

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

statically linked, just as standard Go binaries are? Is isn’t that possible? Thanks! Sander On 22/07/2017, at 19:54 , Sander van Harmelen <san...@xanzy.io> wrote: Yeah I found suggestions like that. But how does that work then? Does that need to be the lib compiled for the target

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

t; On Sat, Jul 22, 2017 at 4:41 AM, Sander van Harmelen <san...@xanzy.io> 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

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

o it seems it doesn’t cross compile libusb first and so is missing those symbols? Guessing a bit here… Any pointers on how to solve this? Sander On 18/07/2017, at 00:11 , Ian Lance Taylor <i...@golang.org> wrote: On Mon, Jul 17, 2017 at 12:53 PM, Sander van Harmelen <san...@xanzy.io>

[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

Re: [go-nuts] How to idiomatically display chained errors?

Did you check the errors package: https://godoc.org/github.com/pkg/errors ? It offers a great way to wrap chained errors. Sander On 4 Feb 2017, at 09:08, so.qu...@gmail.com wrote: Is there a idiomatic recommendation for generally displaying errors resulting from chained methods? The

Re: [go-nuts] $GOPTAH/bin and $PATH

Don’t know if I would call it idiomatic, but (IMO) it makes things easier for a few use cases so I’ve also added $GOPATH/bin to my $PATH :) Sander On 2 Feb 2017, at 11:31: 32, adrian_le...@hushmail.com wrote: Gophers, Is it idiomatic to add $GOPTAH/bin to $PATH in order access a Go

Re: [go-nuts] vim setup for auto go fmt on save.

If you want to develop Go in vim, I would strongly suggest to just install and use the vim-go package/plugin. It will help you with a lot of stuff, but most can be turned of if you don’t want of need it. Sander On 10 Oct 2016, at 08:15: 49, 김용빈 wrote: Hello, How could I