Bug#1059000: mutter : Please add support for loong64

[Simon McVittie]

Control: tags -1 + moreinfo

On Tue, 19 Dec 2023 at 16:07:18 +0800, yalingfang wrote:
> Attach the mutter's patch for loong64.

The attached patch just disables some tests. On most architectures,
especially "ports" architectures, successful tests are the only evidence
we have that the package is functional.

Does this mean that mutter compiles successfully on loong64, but does
not actually work? If it doesn't work yet, then we shouldn't be making
it available to loong64 users yet.

Or is there other evidence that mutter works correctly on loong64, and
a justification for why it's OK to ignore these failing tests?

I know we already ignore test failures on several architectures, but
that's already a bad thing (technical debt), and expanding that workaround
to new architectures seems like the wrong direction to be going in.

One common reason why tests in OpenGL-based packages fail on mips64el and
riscv64 is that the Mesa llvmpipe driver is broken on those architectures
(see #1058687). If this also affects loong64, then I would recommend
that the loong64 community should look into fixing or disabling the
llvmpipe driver so that individual packages don't have to work around
it - from the discussion on #1058687, it seems that the work on that
bug that is being done by the riscv64 community is going to benefit
other architectures as well. Perhaps that includes loong64? If yes,
perhaps you can help them to get that work finished and merged?

>      When I compiled the mutter in Loongarch platform, the mutter and 
> gnome-settings-daemon depend each other.

As far as I can see, the only mutter dependency in gnome-settings-daemon
is for the tests. The standard way to bootstrap this is:

- build gnome-settings-daemon with the nocheck build profile
  (DEB_BUILD_PROFILES=nocheck);

- use that to build mutter;

- use that mutter to build gnome-settings-daemon again, this time with
  tests enabled

Breaking circular dependencies with build profiles is a standard thing
to do while bootstrapping a new architecture:
https://wiki.debian.org/DebianBootstrap

Thanks,
    smcv