-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Remove support for MIPS #412
Comments
Let's just not build stuff in CI unless we release it. If people insist on maintaining build system support for an esoteric config that we don't release, I'm receptive to maintaining 1 CI job to keep us honest about the config working. FWIW I tried to add support for every architecture supported by Debian. https://cdimage.debian.org/debian-cd/current/ has the list from the current Debian version. I assume the Debian folks do a reasonable job of supporting common/popular architectures. If our target is more companies and less enthusiast users, then the set of Linux arches we care about likely reduces to x86-64, aarch64/arm64, and ppc64le (to support IBM servers). +1 from me on at least deleting most CI for |
This is very helpful context, thank you!
👍 yeah I'm not in a rush here, we can see if there's any community feedback. |
Some additional context on the state of MIPS in Debian at https://wiki.debian.org/MIPSPort
|
This discussion is prompted by python/cpython#127708 (comment)
We do not release or test these distributions, but we build them.
We build the following targets for all Python verisons:
mips-unknown-linux-gnu
mipsel-unknown-linux-gnu
It also looks like there's support in the code for
mips64el-unknown-linux-gnuabi64
but we don't build them in CI.I don't think these targets merit the compute and maintenance time. I propose just removing them from the project.
Please comment here if you're using these builds.
The text was updated successfully, but these errors were encountered: