Bug#1095462: sysprof :FTBFS:build failed ( error: ‘PERF_REG_EXTENDED_MASK’ undeclared (first use in this function))

Bo YU tsu.yubo at gmail.com
Sat Feb 8 10:10:19 GMT 2025


Hi,

On Sat, Feb 08, 2025 at 03:50:34PM +0800, Yue Gui wrote:
>   Source: sysprof
>   Version:  48~beta-1
>   Severity: serious
>   Tags: FTBFS, patch
>   User: [1]debian-riscv at lists.debian.org
>   Usertags: riscv64
>   X-Debbugs-Cc: [2]debian-riscv at lists.debian.org

...
>   [3]https://buildd.debian.org/status/fetch.php?pkg=sysprof&arch=riscv64&
>   ver=48%7Ebeta-1&stamp=1738975361&raw=0
>   My solution to this issue:
>     The cause of this error is that the code uses the macro
>   "PERF_REG_EXTENDED_MASK" on a non-x86 architecture, whereas this macro
>   is typically defined only on x86 platforms (or after including certain
>   x86 header files).   To resolve this issue, you can adopt a conditional
>   check approach: if a non‑x86 platform is detected or if
>   PERF_REG_EXTENDED_MASK is not defined, provide an appropriate default
>   value (for example, 0ULL).The debpatch is in the attachment.I have
>   tested it locally and it works well.Please let me know whether this
>   solution can be accepted.

If I understand correctly, this build issue is not specific to riscv64,
so we do not need d-riscv list usertags tagged by riscv64 for it special.
We use usertag to classify a certain issues which has the same, like
the behavior or cause to let developer/maintainer has an overall understanding.
Here you can visit d-riscv list usertag[0] to have a look at issues related 
to riscv64.

In theory, as porters, you can cc all architectures(tagged with $arch)
to let other porters to realize this. But if looking at this[1] again, I
think you will not to do this.:)

BTW, when submitting patch to Debian, it is encouraged to obey Patch
Tagging Guidelines[2]. When you filling these terms of dep3 you will
find one interesting entry: forwarded or upstream unless this issue is
debian specific. In other words, we can forward the patch to upstream
when send to debian meantime.

Thanks for your contribution!

[0]:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-riscv@lists.debian.org&tag=riscv64

[1]: https://buildd.debian.org/status/package.php?p=sysprof&suite=sid

[2]: https://dep-team.pages.debian.net/deps/dep3/


>   Gui-Yue
>   Best Regards
>
>References
>
>   1. mailto:debian-riscv at lists.debian.org
>   2. mailto:debian-riscv at lists.debian.org
>   3. https://buildd.debian.org/status/fetch.php?pkg=sysprof&arch=riscv64&ver=48~beta-1&stamp=1738975361&raw=0



-- 
Regards,
--
   Bo YU

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20250208/28a8d4a7/attachment.sig>


More information about the pkg-gnome-maintainers mailing list