Re: building newt using go

On Thu, Mar 09, 2017 at 07:52:58AM +, David Brown wrote: > I would suggest we remove this particular dependency. Although it is nice > to have symbolic names, go 1.6 is the latest version that is in a LTS > ubuntu release, so I suspect it is the easiest version for a lot of people > to have

Re: building newt using go

Noted. The docs will be updated with the newer version. thanks, aditi > On Mar 8, 2017, at 3:36 AM, Simon Ratner wrote: > > Note to devs: docs still say "The Newt tool requires Go version 1.5 or > later." > http://mynewt.apache.org/latest/newt/install/newt_linux/ > > On Tue,

Re: building newt using go

Thanks! That is quite helpful. On Tue, Mar 7, 2017 at 6:35 PM, Simon Ratner wrote: > Hey Bill, > > I ran into that recently, grab a newer version of go. > This constant was added in 1.7: https://golang.org/doc/go1.7#io > > On Tue, Mar 7, 2017 at 6:10 PM, Bill Rees

Re: building newt using go

Note to devs: docs still say "The Newt tool requires Go version 1.5 or later." http://mynewt.apache.org/latest/newt/install/newt_linux/ On Tue, Mar 7, 2017 at 6:35 PM, Simon Ratner wrote: > Hey Bill, > > I ran into that recently, grab a newer version of go. > This constant was

Re: building newt using go

Hey Bill, I ran into that recently, grab a newer version of go. This constant was added in 1.7: https://golang.org/doc/go1.7#io On Tue, Mar 7, 2017 at 6:10 PM, Bill Rees wrote: > I'm in a virtual box environment with Ubuntu yakkety and have installed go > 1.6. When I build

building newt using go

I'm in a virtual box environment with Ubuntu yakkety and have installed go 1.6. When I build newt ala "go install" I see an error: "undefined io.SeekCurrent" for which I can find no value. Is this a sign of a bad install? A missing module? Thanks, Bill Rees --