On Sun, 24 Mar 2024 at 00:36:11 +0000, Thorsten Glaser wrote:
> libunwind-dev is not available for at least alpha, hurd-any,
> loong64, m68k, sparc64, x32.
>
> sysprof is a not unimportant part in the GNOME dependency chain
> (IIRC seeing it for weston) and part of the t64 transition, so
> having it generally available (with missed features if needed)
> is needed.
Another possible way to attack this, particularly if libunwind is
functionally necessary in sysprof (I don't know whether it is), would
be to limit sysprof integration to those architectures where developers
are practically likely to want to carry out profiling/optimization work.
In general sysprof is an optional dependency: the purpose of compiling
lower-level libraries like GTK with sysprof integration is to get more
detailed profiling and performance reporting, but that's probably only
interesting on relatively mainstream architectures where a developer
is more likely to be making use of that information.
(Or of course porting libunwind to the remaining architectures would
be another obvious way that porters could address this.)
smcv
