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

Add ARM build configurations to CI and release workflows #2702

Merged
merged 2 commits into from
Jan 6, 2024

Conversation

yelkarama
Copy link
Contributor

Add the following targets:

  • armv7-unknown-linux-gnueabihf
  • armv7-unknown-linux-musleabi
  • armv7-unknown-linux-musleabihf

@BurntSushi
Copy link
Owner

Could you say why you opened #2700 and #2701 too? This should only need one PR.

@yelkarama
Copy link
Contributor Author

yelkarama commented Jan 5, 2024

Please ignore the other 2. I was trying to push another commit in a separate branch, but it ended up (twice) in the master branch and it was included in the PR. I had to close them and submit this one instead.

@BurntSushi
Copy link
Owner

Hmm okay. Just so you're aware, you can rebase and force push.

@BurntSushi
Copy link
Owner

How did you test this? You have to run the release workflow and ensure the binaries are produced in a fork. Right now, it fails because the armv7-unknown-linux-musleabi target doesn't seem to have a Docker image:

$ docker run -it rustembedded/cross:armv7-unknown-linux-musleabi bash
Unable to find image 'rustembedded/cross:armv7-unknown-linux-musleabi' locally
docker: Error response from daemon: manifest for rustembedded/cross:armv7-unknown-linux-musleabi not found: manifest unknown: manifest unknown.
See 'docker run --help'.

Ah okay... It looks like the Cross project changed this around. Sigh. It's now here:

$ docker run -it ghcr.io/cross-rs/x86_64-unknown-linux-musl:main bash
root@45607f50d74d:/# exit

yelkarama and others added 2 commits January 6, 2024 10:14
... it turns out that rustembedded/cross:armv7-unknown-linux-musleabi
doesn't exist. And looking more closely, it looks like the Cross project
has decided to shake things up and publish images to ghcr instead. So we
migrate everything over to that.
It looks like these aren't needed any more? I'm not sure why to be
honest. I suspect it's because we no longer need asciidoc(tor)? to
generate man pages. And I believe tests that require things like `zstd`
are automatically if `zstd` isn't installed.
@BurntSushi
Copy link
Owner

Switching everything over to ghcr.io was a bit of a pain. It also turned out that we don't need the old custom images I was maintaining any more. But that was probably true before.

@BurntSushi BurntSushi merged commit 5dec4b8 into BurntSushi:master Jan 6, 2024
17 checks passed
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request Jan 8, 2024
14.1.0
======
This is a minor release with a few small new features and bug fixes. This
release contains a bug fix for unbounded memory growth while walking a
directory tree. This release also includes improvements to the completions for
the `fish` shell, and release binaries for several additional ARM targets.

Bug fixes:

* [BUG #2664](BurntSushi/ripgrep#2690):
  Fix unbounded memory growth in the `ignore` crate.

Feature enhancements:

* Added or improved file type filtering for Lean and Meson.
* [FEATURE #2684](BurntSushi/ripgrep#2684):
  Improve completions for the `fish` shell.
* [FEATURE #2702](BurntSushi/ripgrep#2702):
  Add release binaries for `armv7-unknown-linux-gnueabihf`,
  `armv7-unknown-linux-musleabihf` and `armv7-unknown-linux-musleabi`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants