goinstall problem: properties.go

[GoogleCodeExporter]

$ goinstall goprotobuf.googlecode.com/hg/proto
/opt/local/bin/bash: === cd 
~/local/go/src/pkg/goprotobuf.googlecode.com/hg/proto; bash gomake -f- install
6g -I "~/local/go/pkg/darwin_amd64"  -o _go_.6 decode.go encode.go 
extensions.go lib.go message_set.go properties.go text.go text_parser.go 
properties.go:151: too many arguments in call to strings.Split
properties.go:250: cannot use 1 (type uintptr) as type int in assignment
properties.go:251: cannot use 1 (type uintptr) as type int in assignment
properties.go:255: cannot use 4 (type uintptr) as type int in assignment
properties.go:256: cannot use 4 (type uintptr) as type int in assignment
properties.go:260: cannot use 8 (type uintptr) as type int in assignment
properties.go:261: cannot use 8 (type uintptr) as type int in assignment
properties.go:265: cannot use 4 (type uintptr) as type int in assignment
properties.go:266: cannot use 4 (type uintptr) as type int in assignment
properties.go:270: cannot use 8 (type uintptr) as type int in assignment
properties.go:271: cannot use 8 (type uintptr) as type int in assignment
properties.go:271: too many errors
make: *** [_go_.6] Error 1

I am using the latest version of Go, possibly not released. Could that be the 
problem?

Original issue reported on code.google.com by cdunn2...@gmail.com on 22 Jul 2011 at 5:19

[GoogleCodeExporter]

For first issue, strings.Split has been renamed to SplitN, while the new Split 
drops the last argument and is the same as n=-1.

Original comment by cdunn2...@gmail.com on 22 Jul 2011 at 5:30

[GoogleCodeExporter]

hg update tip
in goprotobuf should fix your problem. it looks like you're at release, not tip.

Original comment by r@golang.org on 23 Jul 2011 at 6:04

• Changed state: Invalid

[GoogleCodeExporter]

hg update tip
in goprotobuf should fix your problem. it looks like you're at release, not tip.

Original comment by r@golang.org on 23 Jul 2011 at 6:04

[GoogleCodeExporter]

Issue 15 has been merged into this issue.

Original comment by r@golang.org on 1 Aug 2011 at 4:53

[GoogleCodeExporter]

Issue 16 has been merged into this issue.

Original comment by r@golang.org on 4 Aug 2011 at 12:17

[GoogleCodeExporter]

I'm still getting that at least with golang 1.58

$ rm -rf /tmp/gopath/
$ mkdir -p /tmp/go
$ GOPATH=/tmp/go goinstall goprotobuf.googlecode.com/hg/proto
/bin/bash: === cd /tmp/go/src/goprotobuf.googlecode.com/hg/proto; bash gomake 
-f- install
6g -I "/tmp/go/pkg/linux_amd64"  -o _go_.6 lib.go text_parser.go text.go 
properties.go message_set.go extensions.go encode.go decode.go 
text.go:61: not enough arguments in call to strings.Split
properties.go:151: not enough arguments in call to strings.Split
properties.go:250: cannot use 1 (type int) as type uintptr in assignment
properties.go:251: cannot use 1 (type int) as type uintptr in assignment
properties.go:255: cannot use 4 (type int) as type uintptr in assignment
properties.go:256: cannot use 4 (type int) as type uintptr in assignment
properties.go:260: cannot use 8 (type int) as type uintptr in assignment
properties.go:261: cannot use 8 (type int) as type uintptr in assignment
properties.go:265: cannot use 4 (type int) as type uintptr in assignment
properties.go:266: cannot use 4 (type int) as type uintptr in assignment
properties.go:266: too many errors
make: *** [_go_.6] Error 1
--- exit status 2
goinstall: installing: running bash: exit status 2
$ cd /tmp/go/src/goprotobuf.googlecode.com/hg/
$ hg update tip
8 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd -
/tmp
$ GOPATH=/tmp/go goinstall goprotobuf.googlecode.com/hg/proto
/bin/bash: === cd /tmp/go/src/goprotobuf.googlecode.com/hg/proto; bash gomake 
-f- install
6g -I "/tmp/go/pkg/linux_amd64"  -o _go_.6 lib.go text_parser.go text.go 
properties.go message_set.go extensions.go encode.go decode.go 
text.go:61: not enough arguments in call to strings.Split
properties.go:151: not enough arguments in call to strings.Split
properties.go:250: cannot use 1 (type int) as type uintptr in assignment
properties.go:251: cannot use 1 (type int) as type uintptr in assignment
properties.go:255: cannot use 4 (type int) as type uintptr in assignment
properties.go:256: cannot use 4 (type int) as type uintptr in assignment
properties.go:260: cannot use 8 (type int) as type uintptr in assignment
properties.go:261: cannot use 8 (type int) as type uintptr in assignment
properties.go:265: cannot use 4 (type int) as type uintptr in assignment
properties.go:266: cannot use 4 (type int) as type uintptr in assignment
properties.go:266: too many errors
make: *** [_go_.6] Error 1
--- exit status 2
goinstall: installing: running bash: exit status 2
$ 

Original comment by fgiunch...@gmail.com on 4 Aug 2011 at 10:42

[GoogleCodeExporter]

I repeat: i have seen this error report many times and it is version skew. 
There is no compilation error in the code, you just have to sort out your go 
and goprotobuf repos to be at the same release point.

Original comment by r@golang.org on 5 Aug 2011 at 12:13

[GoogleCodeExporter]

Original comment by dsymo...@golang.org on 5 Aug 2011 at 6:44

• Changed state: VersionSkew

[GoogleCodeExporter]

So, what versions do match? I am trying to install the following and have been 
trying to do so for many, many hours now: Google App Engine, Go for GAE, 
Protocol Buffers, GoProtoBuf, Goclipse, Gocode... I have gotten everything to 
work now except goprotobuf because of the errors above. GAE uses Go r58.1. 
Which version of protocol buffers and goprotobuf works with that version of go? 
I am getting desperate for help. :)

Original comment by ricky.he...@gmail.com on 28 Sep 2011 at 7:48

[GoogleCodeExporter]

Even besides the versioning problems, you won't be able to use goprotobuf on 
App Engine because it uses the "unsafe" package. We're trying to come up with a 
good solution for that.

On the versioning problem, App Engine will be on r60 pretty soon, so you might 
want to simply wait for that.

Original comment by dsymo...@golang.org on 28 Sep 2011 at 7:53

[GoogleCodeExporter]

Oh... bummer. :) It sounds like an important fix. We are creating a project for 
multiple phone OS's to communicate with a common backend. After a few months of 
research, the ideal things seemed to be:
Backend hosting: Google App Engine
Programming language: Go
Communication to phones: Protocol Buffers

I can't think of a better setup actually so it would be great to get that 
running. I'll use JSON for the beta version of our application.

Thanks for the clarification

Original comment by ricky.he...@gmail.com on 28 Sep 2011 at 8:08