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.

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

Support armv7/8 #801

Closed
Xnyle opened this issue Dec 4, 2018 · 6 comments
Closed

Support armv7/8 #801

Xnyle opened this issue Dec 4, 2018 · 6 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@Xnyle
Copy link

Xnyle commented Dec 4, 2018

Tried to build an arm64 version, tuns out that's not currently possible because:

Build dep uses https://raw.githubusercontent.com/golang/dep/master/install.sh which doesn't support arm.

There is also a pending issue here golang/dep#1807 but it seems nobody cares.

Therefore could the build process altered so that it does not rely on that script?
Or is there a fundamental reason why this project wouldn't run on arm?

@Raffo
Copy link
Contributor

Raffo commented Dec 5, 2018

There is no reason not to support arm64, but unfortunately I believe there are no plans to migrate to another dependency manager just yet. Ideally, we will use go modules in the future, but it's probably too early to jump on that.
We could, in the meantime, add a dedicated Makefile rule to build on arm, and we would be happy to review a PR that introduces such support.

@karlskewes
Copy link

Sent in small PR to golang/dep to add arm and arm64 releases here: golang/dep#2102
It's linked on that issue too.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 11, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants