What steps will reproduce the problem?
1. either goinstall goprotobuf.googlecode.com/hg/proto or get the package and
gomake.
What is the expected output? What do you see instead?
should compile.
What version of the product are you using? On what operating system?
Linux jimx 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:05:41 UTC 2011 i686
i686 i386 GNU/Linux
go:
changeset: 9315:43d0a011c089
tag: tip
user: Dave Cheney <dave@cheney.net>
date: Sun Jul 31 19:54:47 2011 -0700
summary: 5g: fix set but not used error
goprotobuf:
changeset: 81:da17c98c73d8
tag: tip
user: David Symonds <dsymonds@golang.org>
date: Fri Jul 22 14:54:17 2011 +1000
summary: goprotobuf: Detect and return a useful error if someone passes T
(instead of *T) to proto.Marshal.
Please provide any additional information below.
Compile error:
cd proto && gomake install
make[1]: Entering directory
`/home/jimxu/go/src/pkg/goprotobuf.googlecode.com/hg/proto'
8g -o _go_.8 encode.go decode.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 4 (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 4 (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[1]: *** [_go_.8] Error 1
make[1]: Leaving directory
`/home/jimxu/go/src/pkg/goprotobuf.googlecode.com/hg/proto'
make: *** [install] Error 2
Should be easy to fix though.
Original issue reported on code.google.com by i3dmas...@gmail.com on 1 Aug 2011 at 3:59
Original issue reported on code.google.com by
i3dmas...@gmail.com
on 1 Aug 2011 at 3:59