Dear maintainers,

Compiling mono for loong64 has been failing in the Debian Package
Auto-Building environment.
After analysis, I found that upstream Mono's support for the loongarch64
architecture is already in the main branch.
The link is: https://gitlab.winehq.org/mono/mono/-/tree/main?ref_type=heads

I would like to get the maintainer's advice: should we backport the main
branch patches to 6.14.1+ds2-3, or wait for upstream to release a new
version?

Best regards,
Dandan Zhang

Hi Dandan,

Thank you for the report and for pointing at the upstream work.

The short answer is: the right path here is to wait for upstream to
tag a release that includes loongarch64 support, rather than backporting
unreleased main branch patches into the Debian 6.14.1 package.

The loongarch64 port in the upstream main branch is a substantial new
architecture target with JIT codegen, ABI-specific calling conventions,
exception handling, and GC support.  Carrying that as a Debian-only patch
set against 6.14.1 would impose a significant maintenance burden on every
future upstream import, and it would be based on unreleased code that has
not yet gone through upstream's own release process.

The most effective path forward is for Loongson to work with the upstream
Mono maintainers [1] to get a release tagged that includes the loong64
support.  Once that happens, Debian can do a new import/release and
loong64 will be included in the Architecture list naturally.

I am tagging this bug "upstream" to reflect that the fix must come from
an upstream release.  The "ftbfs" tag stays, as that accurately describes
the current state on loong64.

Best,
James

[1] https://gitlab.winehq.org/mono/mono