The LoongArch ISA is used on CPUs created by Loongson, who have internally created a loongarch64 port that they have turned into an unofficial Debian port called loong64.
Porterbox
There is currently a porter box shenzhou.debian.net. You can also set up your own loong64 sbuild chroot with LoongArch/sbuildQEMU
References
Status: unofficial loong64 port accepted
Discussions: <c32d3af9f9ebc362431e2f208f75b52ba64779c0.camel@physik.fu-berlin.de> <b5a53692-592c-2e3d-a996-a8d6692f4eb1@loongson.cn> <12133b5.b049.182493b9628.Coremail.sangmeng@loongson.cn> <Y0FqIwOJuBMGGHxZ@thunder.hadrons.org> <OS0P286MB0641F6E5B9C3AE7434E9638ACD369@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM> <37f3f5f2.5495.18432e942d7.Coremail.sangmeng@loongson.cn><1bcbfd39.6450.1843d9f7e2c.Coremail.zhangdandan@loongson.cn>
Mailing list: debian-loongarch (request)
IRC channels: #debian-loongarch, #debian-bootstrap, #debian-ports on OFTC
Documentation: https://loongson.github.io/LoongArch-Documentation/
Unofficial FAQ: https://blog.xen0n.name/en/posts/tinkering/loongarch-faq/
Other pages
Resources
Mailing list
IRC
irc.oftc.net / irc.debian.org (https://www.oftc.net/)
- #debian-loongarch
Bugs (BTS)
- loong64: all bugs related to the Debian loong64 port
bugs.debian.org/usertags examples:
Submitting a new bug:
To: submit@bugs.debian.org Subject: foo: FTBFS on loong64 Package: foo Version: 1.2.3-4 Severity: wishlist X-Debbugs-CC: debian-loongarch@lists.debian.org Tags: ftbfs User: debian-loongarch@lists.debian.org Usertags: loong64 The version of the package currently FTBFS on the loong64 port: URL_of_the_log
Tagging an existing bug:
To: control@bugs.debian.org Subject: loong64 usertags for #BUGNUMBER CC: debian-loongarch@lists.debian.org user debian-loongarch@lists.debian.org usertag BUGNUMBER + loong64 stop
FTBFS, packages that Fail To Build From Source (in loong64)
Breno Leitão or other people created the following script, which lists packages that currently fail to build in loong64, classifying them by number of arches in which it fails (e.g. only in loong64 or in more than this one) or if there are pending patches or not, etc.; and with links to several related places handy to have (e.g. build logs, BTS).
So it's a nice place to start looking at things that need to be fixed.