go tool: no such tool "compile"

[JM]

Im running go 1.5 with:

go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\GoPath
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1

and when i try to:

C:\Go\src>go get github.com/jasonmoo/lambda_proc
the error is:
go tool: no such tool "compile"

I'm trying to use this package which is a helper to allow me to kick off a golang package from node running inside of aws lambda.
aws lambda which runs on linux/amd64.  There are 2 issues it seems, one i get this package downloaded and 2, i need to build my code with the binaries for amd/linux and i am on windows.

Any help???

Thanks.

[Jeff Mangan]

i found this: https://gist.github.com/booherbg/f812c9145d157d8945b2

but it looks like i need the reverse windows >> linux

--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/iTCTqG_JcW0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ian Lance Taylor]

On Wed, Mar 23, 2016 at 1:58 PM, JM <je...@magentatech.com> wrote:
> Im running go 1.5 with:
>
> go env
> set GOARCH=amd64
> set GOBIN=
> set GOEXE=.exe
> set GOHOSTARCH=amd64
> set GOHOSTOS=windows
> set GOOS=windows
> set GOPATH=C:\GoPath
> set GORACE=
> set GOROOT=C:\Go
> set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
> set GO15VENDOREXPERIMENT=
> set CC=gcc
> set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
> set CXX=g++
> set CGO_ENABLED=1
>
> and when i try to:
>
> C:\Go\src>go get github.com/jasonmoo/lambda_proc
> the error is:
> go tool: no such tool "compile"

Most likely your GOROOT does not match the go binary that is on your
PATH. If you built go yourself you should not need to set GOROOT at
all.

Ian

[JM]

i don't have enough go experience to know what your referring to here, can you elaborate?

1) Most likely your GOROOT does not match the go binary that is on your

PATH. 

2) If you built go yourself you should not need to set GOROOT at
all.

Ian

[Ian Lance Taylor]

On Thu, Mar 24, 2016 at 9:11 AM, JM <je...@magentatech.com> wrote:
> i don't have enough go experience to know what your referring to here, can
> you elaborate?

I am guessing that you have explicitly set the variable GOROOT in your
environment.

If you built Go yourself, do not do that.

Ian

> 1) Most likely your GOROOT does not match the go binary that is on your
>>
>> PATH.
>>
>> 2) If you built go yourself you should not need to set GOROOT at
>> all.
>>
>> 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