[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1033130: gcc-snapshot: FTBFS on hppa - sys/mman.h: No such file or directory



Source: gcc-snapshot
Version: 1:20230315-1
Severity: normal
Tags: ftbfs

Dear Maintainer,

Build fails with following error:
/<<PKGBUILDDIR>>/build-hppa64/./gcc/xgcc -B/<<PKGBUILDDIR>>/build-hppa64/./gcc/ -B/usr/lib/gcc-snapshot/hppa64-linux-gnu/bin/ -B/usr/lib/gcc-snapshot/hppa64-linux-gnu/lib/ -isystem /usr/lib/gcc-snapshot/hppa64-linux-gnu/include -isystem /usr/lib/gcc-snapshot/hppa64-linux-gnu/sys-include    -g -O2 -O2  -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -Dpa64=1 -DELF=1 -DLINUX=1 -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fPIC -Dpa64=1 -DELF=1 -DLINUX=1 -I. -I. -I../.././gcc -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc -I../../../src/libgcc/../include     -o _gcov_merge_add.o -MT _gcov_merge_add.o -MD -MP -MF _gcov_merge_add.dep -DL_gcov_merge_add -c ../../../src/libgcc/libgcov-merge.c
In file included from ../../../src/libgcc/libgcov-merge.c:26:
../../../src/libgcc/libgcov.h:49:10: fatal error: sys/mman.h: No such file or directory
   49 | #include <sys/mman.h>
      |          ^~~~~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:924: _gcov_merge_add.o] Error 1

We have in libgcov.h:

#if HAVE_SYS_MMAN_H
#include <sys/mman.h>
#endif

Either configure is broken or there is a problem with the include paths:

checking for sys/auxv.h... yes
checking for sys/mman.h... yes

Regards,
Dave Anglin

-- System Information:
Debian Release: 12.0
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 6.1.20+ (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)


Reply to: