Control: fixed -1 7.2.0~b1-1 On 6/6/25 05:57, Yue Gui wrote:
Source: papi Version: 7.1.0-5 Severity: serious
Why the high severity? The RISC-V FTBFS is not a regression ...
My solution to this issue: The issue is caused by the lack of RISC-V support in papi. Therefore, it can be resolved by adding support for RISC-V. I referred to an upstream PR and added support for RISC-V accordingly( https://github.com/icl-utk-edu/papi/pull/149).The debdiff patch is in the attachment.I have tested that locally, and it works well. Please let me know whether this solution can be accepted.
That has been incorporated upstream and is already available in the beta releases in experimental.
Is there a good reason for getting this patch into trixie at this stage of the freeze? The two reverse build-depends of papi (eztrace and starpu) do have riscv64 builds (probably because they exclude riscv64 in the libpapi-dev B-D) and as long as libpfm4 does not support riscv64 papi is only a stub (as you wrote in your github PR) and linking them against libpapi is not really an improvement. (But for forky and once papi 7.2 is released, we should revise the libpapi-dev B-D of eztrace and starpu.)
Andreas
