can't load package: package .: no buildable Go source files

后端 未结 7 733
無奈伤痛
無奈伤痛 2020-12-13 03:29

Here is the error message:

% go get     
can\'t load package: package .: no buildable Go source files in /Users/7yan00

% echo $GOPATH     
/Users/7yan00/Gol         


        
相关标签:
7条回答
  • 2020-12-13 03:45

    you can try to download packages from mod

    go get -v all

    0 讨论(0)
  • 2020-12-13 03:53

    If you want all packages in that repository, use ... to signify that, like:

    go get code.google.com/p/go.text/...
    
    0 讨论(0)
  • 2020-12-13 03:55

    You should check the $GOPATH directory. If there is an empty directory of the package name, go get doesn't download the package from the repository.

    For example, If I want to get the github.com/googollee/go-socket.io package from it's github repository, and there is already an empty directory github.com/googollee/go-socket.io in the $GOPATH, go get doesn't download the package and then complains that there is no buildable Go source file in the directory. Delete any empty directory first of all.

    0 讨论(0)
  • 2020-12-13 03:55

    Another possible reason for the message:

    can't load package: .... : no buildable Go source files

    Is when the source files being compiled have:

    // +build ignore
    

    In which case the files are ignored and not buildable as requested.This behaviour is documented at https://golang.org/pkg/go/build/

    0 讨论(0)
  • 2020-12-13 04:01

    To resolve this for my situation:

    I had to specify a more specific sub-package to install.

    Wrong:

    go get github.com/garyburd/redigo
    

    Correct:

    go get github.com/garyburd/redigo/redis
    
    0 讨论(0)
  • 2020-12-13 04:02

    I had this exact error code and after checking my repository discovered that there were no go files but actually just more directories. So it was more of a red herring than an error for me.

    I would recommend doing

    go env

    and making sure that everything is as it should be, check your environment variables in your OS and check to make sure your shell (bash or w/e ) isn't compromising it via something like a .bash_profile or .bashrc file. good luck.

    0 讨论(0)
提交回复
热议问题