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

[Sander van Harmelen]

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 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.8-linaro_uClibc-0.9.33.2.Darwin-x86_64/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mipsel-openwrt-linux-uclibc-gcc-4.8.3
 
PKG_CONFIG_LIBDIR=portaudio-mips/lib/pkgconfig:sphinxbase-mips/lib/pkgconfig:/pocketsphinx-mips/lib/pkgconfig
 go build

# github.com/xlab/pocketsphinx-go/pocketsphinx 
<http://github.com/xlab/pocketsphinx-go/pocketsphinx>
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go:142: type 
[2147483647]byte larger than address space
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go:1248: type 
[2147483647]uint32 larger than address space
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go: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 
<mailto:san...@xanzy.io>> wrote:

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 
<mailto:i...@golang.org>> wrote:

> On Sat, Jul 22, 2017 at 12:57 PM, Sander van Harmelen <san...@xanzy.io 
> <mailto:san...@xanzy.io>> 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 one additional question… Is it possible to make the resulting 
> binary statically linked, just as standard Go binaries are? Is isn’t that 
> possible?

It should be possible, but it kind of depends on your C toolchain.
The basic idea is
  go install -ldflags=-extldflags=-static

Ian


-- 
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...@googlegroups.com 
<mailto:golang-nuts+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout 
<https://groups.google.com/d/optout>.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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.8-linaro_uClibc-0.9.33.2.Darwin-x86_64/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mipsel-openwrt-linux-uclibc-gcc-4.8.3
 
PKG_CONFIG_LIBDIR=portaudio-mips/lib/pkgconfig:sphinxbase-mips/lib/pkgconfig:/pocketsphinx-mips/lib/pkgconfig
 go build

# github.com/xlab/pocketsphinx-go/pocketsphinx
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go:142: type 
[2147483647]byte larger than address space
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go:1248: type 
[2147483647]uint32 larger than address space
../../../xlab/pocketsphinx-go/pocketsphinx/pocketsphinx.go: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 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 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 statically linked, just as standard Go binaries are? Is isn’t that 
> possible?

It should be possible, but it kind of depends on your C toolchain.
The basic idea is
  go install -ldflags=-extldflags=-static

Ian

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 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 statically linked, just as standard Go binaries are? Is isn’t that 
> possible?

It should be possible, but it kind of depends on your C toolchain.
The basic idea is
   go install -ldflags=-extldflags=-static

Ian

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 
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 (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 <i...@golang.org> wrote:

> 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 I end up getting these errors:
> 
> 
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/libusb.cgo2.o:
> In function `_cgo_403ec9e57611_Cfunc_libusb_set_interface_alt_setting':
> libusb.cgo2.c:(.text+0x15bc): undefined reference to
> `libusb_set_interface_alt_setting'
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/libusb.cgo2.o:
> In function `_cgo_403ec9e57611_Cfunc_libusb_unref_device':
> libusb.cgo2.c:(.text+0x16f0): undefined reference to `libusb_unref_device'
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/transfer.o:
> In function `submit':
> transfer.c:(.text+0x40): undefined reference to `libusb_submit_transfer'
> collect2: error: ld returned 1 exit status
> 
> I updated to build command to also include the libusb source: GOOS=linux
> GOARCH=mipsle CGO_ENABLED=1 CC=mipsel-openwrt-linux-uclibc-gcc-4.8.3
> CGO_CFLAGS="-I ./include -I ./libusb-1.0.21/libusb" go build
> 
> So 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?

Something like CGO_LDFLAGS="-lusb", with perhaps a -L option to the
directory where the library exists.

Ian

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 <i...@golang.org> wrote:

> 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 I end up getting these errors:
> 
> 
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/libusb.cgo2.o:
> In function `_cgo_403ec9e57611_Cfunc_libusb_set_interface_alt_setting':
> libusb.cgo2.c:(.text+0x15bc): undefined reference to
> `libusb_set_interface_alt_setting'
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/libusb.cgo2.o:
> In function `_cgo_403ec9e57611_Cfunc_libusb_unref_device':
> libusb.cgo2.c:(.text+0x16f0): undefined reference to `libusb_unref_device'
> /var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/transfer.o:
> In function `submit':
> transfer.c:(.text+0x40): undefined reference to `libusb_submit_transfer'
> collect2: error: ld returned 1 exit status
> 
> I updated to build command to also include the libusb source: GOOS=linux
> GOARCH=mipsle CGO_ENABLED=1 CC=mipsel-openwrt-linux-uclibc-gcc-4.8.3
> CGO_CFLAGS="-I ./include -I ./libusb-1.0.21/libusb" go build
> 
> So 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?

Something like CGO_LDFLAGS="-lusb", with perhaps a -L option to the
directory where the library exists.

Ian

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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/gousb/_obj/libusb.cgo2.o:
 In function `_cgo_403ec9e57611_Cfunc_libusb_set_interface_alt_setting':
libusb.cgo2.c:(.text+0x15bc): undefined reference to 
`libusb_set_interface_alt_setting'
/var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/libusb.cgo2.o:
 In function `_cgo_403ec9e57611_Cfunc_libusb_unref_device':
libusb.cgo2.c:(.text+0x16f0): undefined reference to `libusb_unref_device'
/var/folders/2k/hxm__dq91bj19r7scpr3mzq8gn/T/go-build613045906/github.com/google/gousb/_obj/transfer.o:
 In function `submit':
transfer.c:(.text+0x40): undefined reference to `libusb_submit_transfer'
collect2: error: ld returned 1 exit status

I updated to build command to also include the libusb source: GOOS=linux 
GOARCH=mipsle CGO_ENABLED=1 CC=mipsel-openwrt-linux-uclibc-gcc-4.8.3 
CGO_CFLAGS="-I ./include -I ./libusb-1.0.21/libusb" go build

So 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> 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
> 
> But I receive this error:
> 
> # runtime/cgo
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S: Assembler messages:
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:30: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f20,40($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:31: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f22,48($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:32: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f24,56($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:33: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f26,64($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:34: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f28,72($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:35: Error: opcode not supported on
> this processor: mips32 (mips32) `sdc1 $f30,80($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:52: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f20,40($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:53: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f22,48($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:54: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f24,56($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:55: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f26,64($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:56: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f28,72($29)'
> /usr/local/go/src/runtime/cgo/gcc_mipsx.S:57: Error: opcode not supported on
> this processor: mips32 (mips32) `ldc1 $f30,80($29)'
> 
> I’ve build mipsel-openwrt-linux-gcc using the docs written down here:
> https://wiki.openwrt.org/doc/howto/build
> 
> Any pointers on how to make this work? Or am I out of luck and did I hit
> road block (i.e. it’s not possible/supported)?

I don't understand that error, as to the best of my knowledge the
mips32 ISA supports the ldc1 and sdc1 instructions.

Is it possible that you need to update your GNU binutils?

Ian

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 receive this error:

# runtime/cgo
/usr/local/go/src/runtime/cgo/gcc_mipsx.S: Assembler messages:
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:30: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f20,40($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:31: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f22,48($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:32: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f24,56($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:33: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f26,64($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:34: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f28,72($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:35: Error: opcode not supported on 
this processor: mips32 (mips32) `sdc1 $f30,80($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:52: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f20,40($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:53: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f22,48($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:54: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f24,56($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:55: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f26,64($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:56: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f28,72($29)'
/usr/local/go/src/runtime/cgo/gcc_mipsx.S:57: Error: opcode not supported on 
this processor: mips32 (mips32) `ldc1 $f30,80($29)'

I’ve build mipsel-openwrt-linux-gcc using the docs written down here: 
https://wiki.openwrt.org/doc/howto/build 


Any pointers on how to make this work? Or am I out of luck and did I hit road 
block (i.e. it’s not possible/supported)?

Thanks!

Sander



-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 following would print out "ERROR: Foo() ERROR: Bar() ERROR: stdlib.Func() 
something went wrong with this standard function call", which feels obviously 
wrong.




func main() {
  if err := Foo(); err != nil {
fmt.Printf("ERROR: Foo() %s", err)
os.Exit(1)
  }
}

func Foo() error {
  if err := Bar(); err {
return fmt.Errorf("ERROR: Bar() %s", err)
  }
  return nil
}


func Bar() error {
  if err := stdlib.Func(); err != nil {
return fmt.Errorf("ERROR: stdlib.Func() %s", err)
  }
  return nil
}



-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 executable 
across my filesystem?

Aidy 

-- 
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...@googlegroups.com 
.
For more options, visit https://groups.google.com/d/optout 
.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sander van Harmelen]

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 achieve auto go fmt on save in vim? (with 2~3 lines of code)

I don't want install entire plug-in like vim-go. Or is it better to do?

Thank you.
 

-- 
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...@googlegroups.com 
.
For more options, visit https://groups.google.com/d/optout 
.

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.