Source: libcpucycles Version: 0~20230115-1 Severity: normal After uploading 0~20230115-1 I inspected buildd logs and I noticed that on several architectures like riscv64, arm64, ppc64el and a few others, the package build failed to detect and use architecture-specific timer features and ended using the default common OS-level mechanisms.
More details at: https://buildd.debian.org/status/package.php?p=libcpucycles&suite=sid riscv64 example: ======== [...] riscv32-rdcycle.c:15:2: error: #error this code is only for riscv32 platforms 15 | #error this code is only for riscv32 platforms | ^~~~~ compilation terminated. skipping option that did not compile [...] See more examples with full logs below: https://buildd.debian.org/status/fetch.php?pkg=libcpucycles&arch=arm64&ver=0%7E20230115-1&stamp=1694543693&raw=0 https://buildd.debian.org/status/fetch.php?pkg=libcpucycles&arch=ppc64el&ver=0%7E20230115-1&stamp=1694543637&raw=0 https://buildd.debian.org/status/fetch.php?pkg=libcpucycles&arch=riscv64&ver=0%7E20230115-1&stamp=1694545286&raw=0 -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-24-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche
