Origin: cmd/oc wants gssapi/gssapi.h

[dmage]

$ ./hack/build-go.sh cmd/oc
++ Building go targets for linux/amd64: cmd/oc
# github.com/openshift/origin/vendor/github.com/apcera/gssapi
vendor/github.com/apcera/gssapi/buffer.go:9:27: fatal error: gssapi/gssapi.h: No such file or directory
compilation terminated.

/cc @mfojtik

[mfojtik]

@deads2k seems like this was introduced by glide bump.

[mfojtik]

/cc @enj since this is likely related to krb support.

[deads2k]

I don't think that's new. Came in ages ago when we added support, right?

On Wed, Dec 6, 2017 at 7:37 AM, Michal Fojtik [e-mail]
wrote:

/cc @enj https://github.com/enj since this is likely related to krb
support.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin/issues/17621#issuecomment-349627055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH2BSjcx07OG0Y6H8qvGcVDIVyNgRb_Gks5s9oqSgaJpZM4Q3s5R
.

[dmage]

No,

~/src/github.com/openshift/origin (master)$ git checkout v3.7.0
~/src/github.com/openshift/origin ((v3.7.0))$ ./hack/build-go.sh cmd/oc
++ Building go targets for linux/amd64: cmd/oc
[INFO] hack/build-go.sh exited with code 0 after 00h 01m 10s
~/src/github.com/openshift/origin ((v3.7.0))$ git checkout master
~/src/github.com/openshift/origin (master)$ ./hack/build-go.sh cmd/oc
++ Building go targets for linux/amd64: cmd/oc
# github.com/openshift/origin/vendor/github.com/apcera/gssapi
vendor/github.com/apcera/gssapi/buffer.go:9:27: fatal error: gssapi/gssapi.h: No such file or directory
compilation terminated.

$ git bisect start master v3.7.0
$ git bisect run ./hack/build-go.sh cmd/oc
1a8b960ce025a09f5e3e244c0836c9850c9ce3ca is the first bad commit

[enj]

Seems like we went from requiring GSSAPI only when the flags are set to always requiring it? No sure I care too much, but @stevekuznetsov or @smarterclayton will probably have some thoughts.

cc @simo5

[stevekuznetsov]

Yeah, the linked commit from @smarterclayton does change build flags. I'd expect that to be the issue.

[pmorie]

You can work around this by installing the krb5-devel package.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[stevekuznetsov]

/close