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

ooniprobe: build armv6 binaries #1753

Closed
2 of 3 tasks
bassosimone opened this issue Aug 21, 2021 · 3 comments
Closed
2 of 3 tasks

ooniprobe: build armv6 binaries #1753

bassosimone opened this issue Aug 21, 2021 · 3 comments
Assignees

Comments

@bassosimone
Copy link
Contributor

bassosimone commented Aug 21, 2021

These are the sub-activities:

  • figure out how to compile for armv6 (more precisely: armv6l)
  • ensure the compiled binaries work on Raspbian
  • figure out if we can publish these binaries in our Debian repo or whether Raspbian needs a different repo (i.e., whether the same binaries work with both Debian using armv6 - if it ever exists - and Raspbian)

Related links:

  1. https://github.com/mdtita/oonionpie
  2. https://github.com/masaarnet/Install-OONI-Probe-CLI-on-Raspberry-Pi
@bassosimone bassosimone self-assigned this Aug 21, 2021
@alimirjamali
Copy link

I can confirm a successful build using the latest Golang release (go1.17.linux-armv6l.tar.gz)

@bassosimone
Copy link
Contributor Author

Since ooni/probe-cli#904, we build ooniprobe for armv6! 🚀

I guess the only remaining step is to publish a Debian package.

bassosimone added a commit to ooni/probe-cli that referenced this issue Aug 29, 2022
Part of ooni/probe#1753.

While there, introduce a rule by which, if the branch is named `fullbuild` we run all possible builds. It helps to test all the builds without creating a release branch. Because release branches are protected, they cannot be deleted easily. On the contrary, the `fullbuild` branch can easily be disposed of.
@bassosimone
Copy link
Contributor Author

We're now creating Debian packages for linux armel. Unclear if this is enough to also fix #1960.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants