aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorWANG Xuerui <git@xen0n.name>2025-06-16 16:16:55 +0800
committerVladimir Mezentsev <vladimir.mezentsev@oracle.com>2025-06-30 09:32:05 -0700
commit304662234dc65961a2b01628e1d4c7a612da9bf5 (patch)
tree25c4a008cc7880f306a6bde0de892a2cc6a7e142 /gdb/python/python.c
parent88c66eca24b5fae7d411a2dda342e5a87f4a2d72 (diff)
downloadbinutils-304662234dc65961a2b01628e1d4c7a612da9bf5.zip
binutils-304662234dc65961a2b01628e1d4c7a612da9bf5.tar.gz
binutils-304662234dc65961a2b01628e1d4c7a612da9bf5.tar.bz2
RISC-V: [gprofng] Allow building gprofng without asm/hwprobe.h
The code is actually able to gracefully fallback if the syscall number of riscv_hwprobe is not available at build time, but it still depended on the <asm/hwprobe.h> header unconditionally. In certain environments such as one of crosstool-NG's Canadian Cross build step (binutils for host), or one with very outdated kernel headers, the header will not be present, causing the build to fail. While the relevant projects/environments should be fixed nevertheless, a configure-time check for <asm/hwprobe.h> is helpful for fixing gprofng builds with released versions of ct-ng etc. Signed-off-by: WANG Xuerui <git@xen0n.name>
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions