diff options
| author | Valentin Rothberg <rothberg@redhat.com> | 2021-01-19 10:27:01 +0100 |
|---|---|---|
| committer | Valentin Rothberg <rothberg@redhat.com> | 2021-01-20 13:19:06 +0100 |
| commit | f302ce578b49a00de31aacc0c5e845274de3deac (patch) | |
| tree | 818d0d1140ee4ef2911aa56ea580185e3ab1951b /vendor/go.uber.org/atomic | |
| parent | 7d024a2fc8c675e4d34e3b34b56b6217a48ef9ce (diff) | |
| download | podman-f302ce578b49a00de31aacc0c5e845274de3deac.tar.gz podman-f302ce578b49a00de31aacc0c5e845274de3deac.tar.bz2 podman-f302ce578b49a00de31aacc0c5e845274de3deac.zip | |
make bindings generation more robuts
The Go gods did not shine upon us trying to understand what's going on
in #9000. The symptom is that `go generate` did not add required
imports to a generated file, ultimately breaking subsequent compilation.
While it still remains unclear *why* Go is behaving like that, the
symptom disappears when `go generate` runs in module mode; that is
without `-mod=vendor` and without `GO111MODULE=off`. This was
reproducible on two separate machines (Ubuntu and Fedora).
Also, when facing an unset GOPATH, set it to Go's default (i.e.,
$HOME/go) and make sure that GOBIN is in PATH since `goimports`
is required by `go generate`.
Fixes: #9000
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'vendor/go.uber.org/atomic')
0 files changed, 0 insertions, 0 deletions