FAQ
I tried to build `cmd/vet` locally and got:

~/go/src/golang.org/x/tools/cmd/vet $
./go build
go tool: no such tool "6g"

And try ./go get golang.org/x/tools/cmd/vet in CI environment in Go 1.4 and
got:

package go/constant: unrecognized import path "go/constant"
package go/importer: unrecognized import path "go/importer"
package go/types: unrecognized import path "go/types"


Seems like this is
from https://github.com/golang/tools/commit/542ffc7e75cf45ac7ad456664a710cd96338fda6.

go/types is migrated to standard package since Go 1.5 so Go 1.4 trying to
go get this package fails.

Since golang.org/x/tools/cmd has no versioning, it seems hard to make go
get work even with gopkg.in/golang/tools.release-branch.go1.4.

Is there any easy way to make go get work for Go 1.4?

Thanks!

Related to https://github.com/coreos/etcd/issues/4149.

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

Search Discussions

  • Krzesimir at Jan 7, 2016 at 4:57 pm

    On Thursday, January 7, 2016 at 12:56:09 AM UTC+1, Gyu-Ho Lee wrote:
    I tried to build `cmd/vet` locally and got:

    ~/go/src/golang.org/x/tools/cmd/vet $
    ./go build
    go tool: no such tool "6g"

    And try ./go get golang.org/x/tools/cmd/vet in CI environment in Go 1.4
    and got:

    package go/constant: unrecognized import path "go/constant"
    package go/importer: unrecognized import path "go/importer"
    package go/types: unrecognized import path "go/types"


    Seems like this is from
    https://github.com/golang/tools/commit/542ffc7e75cf45ac7ad456664a710cd96338fda6
    .

    go/types is migrated to standard package since Go 1.5 so Go 1.4 trying to
    go get this package fails.

    Since golang.org/x/tools/cmd has no versioning, it seems hard to make go
    get work even with gopkg.in/golang/tools.release-branch.go1.4.

    Is there any easy way to make go get work for Go 1.4?

    Thanks!

    Related to https://github.com/coreos/etcd/issues/4149.
      In our case (rkt) we downgraded go 1.4 from 1.4.3 to 1.4.2, so we could
    use the vet tool in the tarball instead of building it with go get. With
    semaphore CI this would require some more gimmicks, since semaphore
    provides 1.4.3 only from 1.4 line.

    Instead, it would be nice for Google to make a (final?) release of go 1.4
    series, which would include those tools again in the tarball, but, I don't
    remember exactly where, somebody said it has low priority.

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Adonovan at Jan 7, 2016 at 8:05 pm

    On Wednesday, 6 January 2016 18:56:09 UTC-5, Gyu-Ho Lee wrote:
    I tried to build `cmd/vet` locally and got:

    ~/go/src/golang.org/x/tools/cmd/vet $
    ./go build
    go tool: no such tool "6g"

    And try ./go get golang.org/x/tools/cmd/vet in CI environment in Go 1.4
    and got:

    package go/constant: unrecognized import path "go/constant"
    package go/importer: unrecognized import path "go/importer"
    package go/types: unrecognized import path "go/types"


    Seems like this is from
    https://github.com/golang/tools/commit/542ffc7e75cf45ac7ad456664a710cd96338fda6
    .

    go/types is migrated to standard package since Go 1.5 so Go 1.4 trying to
    go get this package fails.

    Since golang.org/x/tools/cmd has no versioning, it seems hard to make go
    get work even with gopkg.in/golang/tools.release-branch.go1.4.

    Is there any easy way to make go get work for Go 1.4?

    Thanks!

    Related to https://github.com/coreos/etcd/issues/4149.
    Sorry about that; there's been a lot of churn in the tools repo this week
    trying to tag everything for 1.4, 1.5 and 1.6 while changing the >=1.5
    tools to use the standard library.

    I just mailed https://go-review.googlesource.com/#/c/18385/ to fix the
    breakage.

    --
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.
  • Gyu-Ho Lee at Jan 7, 2016 at 8:09 pm
    Thanks all! It would be great to lock in go1.4 binaries using something
    like gopkg.in versioning
    and keep improving in go1.5+.


    On Thursday, January 7, 2016 at 12:06:06 PM UTC-8, adon...@google.com wrote:
    On Wednesday, 6 January 2016 18:56:09 UTC-5, Gyu-Ho Lee wrote:

    I tried to build `cmd/vet` locally and got:

    ~/go/src/golang.org/x/tools/cmd/vet $
    ./go build
    go tool: no such tool "6g"

    And try ./go get golang.org/x/tools/cmd/vet in CI environment in Go 1.4
    and got:

    package go/constant: unrecognized import path "go/constant"
    package go/importer: unrecognized import path "go/importer"
    package go/types: unrecognized import path "go/types"


    Seems like this is from
    https://github.com/golang/tools/commit/542ffc7e75cf45ac7ad456664a710cd96338fda6
    .

    go/types is migrated to standard package since Go 1.5 so Go 1.4 trying to
    go get this package fails.

    Since golang.org/x/tools/cmd has no versioning, it seems hard to make go
    get work even with gopkg.in/golang/tools.release-branch.go1.4.

    Is there any easy way to make go get work for Go 1.4?

    Thanks!

    Related to https://github.com/coreos/etcd/issues/4149.
    Sorry about that; there's been a lot of churn in the tools repo this week
    trying to tag everything for 1.4, 1.5 and 1.6 while changing the >=1.5
    tools to use the standard library.

    I just mailed https://go-review.googlesource.com/#/c/18385/ to fix the
    breakage.
    --
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJan 6, '16 at 11:56p
activeJan 7, '16 at 8:09p
posts4
users3
websitegolang.org

3 users in discussion

Gyu-Ho Lee: 2 posts Krzesimir: 1 post Adonovan: 1 post

People

Translate

site design / logo © 2022 Grokbase