Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enable GSSAPI in darwin release builds #9782

Open
liggitt opened this issue Jul 11, 2016 · 3 comments
Open

Enable GSSAPI in darwin release builds #9782

liggitt opened this issue Jul 11, 2016 · 3 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3

Comments

@liggitt
Copy link
Contributor

liggitt commented Jul 11, 2016

hack/build-go.sh cmd/oc -tags=gssapi produces an oc client capable of speaking Kerberos.

However, the release builds (defined in origin.spec and hack/build-cross.sh) run on Linux, and are not able to cross-compile to Darwin AND perform a cgo-enabled build.
@liggitt liggitt self-assigned this Jul 11, 2016
@liggitt liggitt changed the title Enable GSSAPI in darwin builds Enable GSSAPI in darwin release builds Jul 11, 2016
@mfojtik mfojtik assigned enj and unassigned liggitt Aug 31, 2016
@enj
Copy link
Contributor

enj commented Oct 19, 2016

I see 4 possible ways to approach this:

  1. Use Travis' macOS builders to build oc with CI
  2. On one of our macs, build github.com/apcera/gssapi with -buildmode=shared and use that binary on linux with CI for the darwin builds (not sure if this will work)
  3. Create some type of dynamic runtime linking wrapper like github.com/alexbrainman/sspi but for gssapi and use this on darwin with CI
  4. Build oc on our macs with no CI

@enj enj added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 9, 2017
@liggitt liggitt mentioned this issue Apr 10, 2018
Closed
@openshift-bot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 17, 2018
@enj enj added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 26, 2018
@openshift-ci-robot openshift-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/enhancement labels Apr 14, 2019
@enj
Copy link
Contributor

enj commented Oct 16, 2019

/unassign

@stlaz @sttts @mfojtik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@liggitt @openshift-bot @bparees @enj @openshift-ci-robot