From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: Our mips64el support is really really dead
Date: Thu, 27 Jun 2024 14:54:21 +0100 [thread overview]
Message-ID: <87wmma3302.fsf@cbaines.net> (raw)
In-Reply-To: <Zn02MbLyXdnrLTtK@3900XT> (Efraim Flashner's message of "Thu, 27 Jun 2024 12:51:45 +0300")
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Efraim Flashner <efraim@flashner.co.il> writes:
> Three initial bits about Guix's support for mips64el:
> 1. We stopped producing a standalone installer for mips64el before the
> 1.0 release, which means it's been years since anyone has been able to
> install it without help. Actually, 0.12 was the last version¹, back in
> 2016.
> 2. We supported the Lemote Fuloong 2F²/Loongson 2 (MIPS III) processors.
> Except for very specific sticks of RAM, it only supported 1GB of RAM. As
> for the processor, I believe most other distributions moved to the
> Loongson 3 as their base. Debian³ 9 (in 2017) it seems switched to
> Loongson 3A/3B based machines for their Loongson support.
> 3. "Generic" --target=mips64el-linux-gnu support from the GNU toolchain
> doesn't support Loongson 2 chips, it needs some extra flags. I tested
> this a few years ago and wasn't able to run a cross-compiled package on
> one of our decommissioned mips64el build machines (citation needed).
>
> I suggest that we stop cross-compiling packages to mips64el since it is
> really dead-dead, and not just mostly-dead or nearly-dead.
What does this mean for mips64el-linux as a system? I have considered
asking about this in the past because keeping it around does have a cost
and we're not trying to build for it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-06-27 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 9:51 Our mips64el support is really really dead Efraim Flashner
2024-06-27 13:35 ` Ludovic Courtès
2024-06-27 13:54 ` Christopher Baines [this message]
2024-06-27 17:11 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmma3302.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.