Re: The future of mipsel port
Florian Lohoff <[email protected]> Mon, 7 Aug 2023 12:12:17 +0200
| Newsgroups | gmane.linux.debian.ports.mips,gmane.linux.debian.devel.general |
|---|---|
| Organization | rfc822 - pure communication |
| Message-ID | <[email protected]> |
Hi, On Mon, Aug 07, 2023 at 10:53:02AM +0200, Aurelien Jarno wrote: > From what I have understood from YunQiang plans, it is currently not > planned to import mipsel on debian-ports. Are you volunteering for > maintaining such a port? I am not interested in mips32r2 as i have no hardware for that. So everything debian-mipsel stretch++ is unusable. > > revert away from mips32r2 back to mips2/mips3 - That change (with > > stretch) basically dropped all of the supported platforms formerly > > supported without a good reason - mips32r2 cpus would have been > > The reason is that many upstream code do not support mips2 anymore, > especially for JIT languages or languages with their own code generator. > Be prepared for a lot of upstream work. I have already started with that on stretch - have 90% build - the issue is that a lot of debian patches unconditionally enabled/switched to mips32r2 Flo -- Florian Lohoff [email protected] Any sufficiently advanced technology is indistinguishable from magic.
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdb9o7oebX2papQ/KkN1BIMsJ8i8FAmTQw4EACgkQkN1BIMsJ 8i/RRA//ZowzovsCRMSo3OUAklxeTta+ZnVoZ08uMhc+IjFj7rZX24FOg440Xgqm fJDCe3T8YGAZXPl43ZOF5q/iKAgkMTwTFirc3WOQYA/ShV+ivo2GM4ncG3nJg7cD R+R9756T9kasbJtXb+KYtv3oCq0/P/i9mL5WO5qUrOyduAB4fVgJdXROnl7IeeL/ Cuxqz1KJnbS97QCWS/SMUsiqDaGpI5MJTigilDZfLIS0il2hrlFp9Q/9T1vQ1MLl nYs0RdFU6hiyEcDJ8n5F0X880fDG+8V2qcj08X/yOk0JBvQehHa3PPQXpX6T/mWM WyEtYxe85w3t1b3xBxOyHnjRT85J0zdFWdz28W470p1iRGjQiTL2cWKwYTcmE1pk b8elRsskXF/YcaBE7kpqzHVVICroM7fd6oqRxP2stZ64ZEBnqijRlbRYFbXK7hJB 3eDqXvWBUnps4sp6wegvQ2OkArBeoYPtcUIr0ne/uLvzQs+xi9bw7EBBAfdaZusY PCdicV3DRQKU2y8aefiEi+qPZiYzb0XDyBu+skPiU7pR/X7amrzwbMSeATBLqzLw 9h2fse0kQp2AUUvOJexKWLkB+vySopWl8oANNPzwdwOuztBLiltlJKqfnudD3KIf gCJQXwyxsA3E++kVIJJfwXrQmpV65kpaSKhERa0Jz4qS1RWznTM= =TaEM -----END PGP SIGNATURE-----