You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go language does not make GOPATH variable mandatory and states that it will default to ~/go when is not defined.
It seems that libpod Makefile is smart enough to detect if code was cloned in an unexpected location and to symlink it to ~/go/src/github.com/containers/libpod but the problem is that this does not make it work.
When this happens go fails to build its dependencies as it end-up looking for them relative to the "resolved" location of podman.
Still, runnning make without GOPATH fails because of this. here is the proof:
This is a serious issue because for non golang developers there are 9/10 changes that exactly this will happen: they will not have GOPATH defined and they will clone the code to another folder.
We need to find a way to make it work when this happens (without requiring any user intervension as this would be key for automating the installation).
I couldn't get the build to work for confusing reasons pertaining to varlink not being found (I'm not familiar with Go) and it turned out it was because I defined the GOPATH to be somewhere else than suggested by the installation README.
Now that I defined it exactly as in the README, the build works as intended.
baude
added a commit
to baude/podman
that referenced
this issue
Feb 13, 2019
when gopath was not explicitly set, make would fail due
to the varlink generator. this symlink in the makefile
addresses that.
fixes: containers#1842
Signed-off-by: baude <[email protected]>
go language does not make GOPATH variable mandatory and states that it will default to
~/go
when is not defined.It seems that libpod Makefile is smart enough to detect if code was cloned in an unexpected location and to symlink it to
~/go/src/github.com/containers/libpod
but the problem is that this does not make it work.When this happens go fails to build its dependencies as it end-up looking for them relative to the "resolved" location of podman.
Still, runnning make without GOPATH fails because of this. here is the proof:
This is a serious issue because for non golang developers there are 9/10 changes that exactly this will happen: they will not have GOPATH defined and they will clone the code to another folder.
We need to find a way to make it work when this happens (without requiring any user intervension as this would be key for automating the installation).
Originally mentioned on #1840
The text was updated successfully, but these errors were encountered: