Bug#975125: perftest: FTBFS: src/perftest_communication.c:532:6: error: redeclaration of ‘enum ibv_gid_type’
Source: perftest
Version: 4.4+0.29-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/perftest_communication.o src/perftest_communication.c
> src/perftest_communication.c:532:6: error: redeclaration of ‘enum ibv_gid_type’
> 532 | enum ibv_gid_type
> | ^~~~~~~~~~~~
> In file included from src/perftest_communication.h:43,
> from src/perftest_communication.c:17:
> /usr/include/infiniband/verbs.h:72:6: note: originally defined here
> 72 | enum ibv_gid_type {
> | ^~~~~~~~~~~~
> src/perftest_communication.c:535:2: error: redeclaration of enumerator ‘IBV_GID_TYPE_ROCE_V2’
> 535 | IBV_GID_TYPE_ROCE_V2,
> | ^~~~~~~~~~~~~~~~~~~~
> In file included from src/perftest_communication.h:43,
> from src/perftest_communication.c:17:
> /usr/include/infiniband/verbs.h:75:2: note: previous definition of ‘IBV_GID_TYPE_ROCE_V2’ was here
> 75 | IBV_GID_TYPE_ROCE_V2,
> | ^~~~~~~~~~~~~~~~~~~~
> gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/perftest_parameters.o src/perftest_parameters.c
> make[2]: *** [Makefile:857: src/perftest_communication.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/perftest_4.4+0.29-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: