-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 CI test for a big-endian target #1193
Comments
Though it's not really useful for "live" testing, we do get post-facto testing from Debian's build infra which has several big-endian targets that will at least tell us if we broke something horribly. i.e., https://buildd.debian.org/status/package.php?p=rust-ripgrep. |
@hlieberman-gov Right, that's how #1144 was reported, AIUI. The point here is to catch problems before they get to the Debian folks. :-) |
This was done in da3431b, which adds a |
Given #1144, it seems prudent for ripgrep to get tested on a big-endian target.
I tried playing with this in #1152 and ran into errors. The
memchr
crate is an example with a big-endian target test that works: https://github.com/BurntSushi/rust-memchr/blob/974943c8bc840538e18d788b6682bbfcdccceb12/.travis.yml#L31-L35The text was updated successfully, but these errors were encountered: