Source: trinity
Version: 1.8-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include 
> config.h -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 
> -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wnested-externs 
> -Wpacked -Wshadow -Wswitch-enum -Wundef -Wwrite-strings 
> -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -fsigned-char 
> -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
> syscalls/x86/modify_ldt.o -c syscalls/x86/modify_ldt.c
> In file included from /usr/include/x86_64-linux-gnu/bits/statx.h:31,
>                  from /usr/include/x86_64-linux-gnu/sys/stat.h:446,
>                  from include/files.h:3,
>                  from include/shm.h:6,
>                  from syscalls/x86/modify_ldt.c:12:
> /usr/include/linux/stat.h:57:2: error: unknown type name ‘__s64’
>    57 |  __s64 tv_sec;
>       |  ^~~~~
> /usr/include/linux/stat.h:58:2: error: unknown type name ‘__u32’
>    58 |  __u32 tv_nsec;
>       |  ^~~~~
> /usr/include/linux/stat.h:59:2: error: unknown type name ‘__s32’
>    59 |  __s32 __reserved;
>       |  ^~~~~
> /usr/include/linux/stat.h:101:2: error: unknown type name ‘__u32’
>   101 |  __u32 stx_mask; /* What results were written [uncond] */
>       |  ^~~~~
> /usr/include/linux/stat.h:102:2: error: unknown type name ‘__u32’
>   102 |  __u32 stx_blksize; /* Preferred general I/O size [uncond] */
>       |  ^~~~~
> /usr/include/linux/stat.h:103:2: error: unknown type name ‘__u64’
>   103 |  __u64 stx_attributes; /* Flags conveying information about the file 
> [uncond] */
>       |  ^~~~~
> /usr/include/linux/stat.h:105:2: error: unknown type name ‘__u32’
>   105 |  __u32 stx_nlink; /* Number of hard links */
>       |  ^~~~~
> /usr/include/linux/stat.h:106:2: error: unknown type name ‘__u32’
>   106 |  __u32 stx_uid; /* User ID of owner */
>       |  ^~~~~
> /usr/include/linux/stat.h:107:2: error: unknown type name ‘__u32’
>   107 |  __u32 stx_gid; /* Group ID of owner */
>       |  ^~~~~
> /usr/include/linux/stat.h:108:2: error: unknown type name ‘__u16’
>   108 |  __u16 stx_mode; /* File mode */
>       |  ^~~~~
> /usr/include/linux/stat.h:109:2: error: unknown type name ‘__u16’
>   109 |  __u16 __spare0[1];
>       |  ^~~~~
> /usr/include/linux/stat.h:111:2: error: unknown type name ‘__u64’
>   111 |  __u64 stx_ino; /* Inode number */
>       |  ^~~~~
> /usr/include/linux/stat.h:112:2: error: unknown type name ‘__u64’
>   112 |  __u64 stx_size; /* File size */
>       |  ^~~~~
> /usr/include/linux/stat.h:113:2: error: unknown type name ‘__u64’
>   113 |  __u64 stx_blocks; /* Number of 512-byte blocks allocated */
>       |  ^~~~~
> /usr/include/linux/stat.h:114:2: error: unknown type name ‘__u64’
>   114 |  __u64 stx_attributes_mask; /* Mask to show what's supported in 
> stx_attributes */
>       |  ^~~~~
> /usr/include/linux/stat.h:121:2: error: unknown type name ‘__u32’
>   121 |  __u32 stx_rdev_major; /* Device ID of special file [if bdev/cdev] */
>       |  ^~~~~
> /usr/include/linux/stat.h:122:2: error: unknown type name ‘__u32’
>   122 |  __u32 stx_rdev_minor;
>       |  ^~~~~
> /usr/include/linux/stat.h:123:2: error: unknown type name ‘__u32’
>   123 |  __u32 stx_dev_major; /* ID of device containing file [uncond] */
>       |  ^~~~~
> /usr/include/linux/stat.h:124:2: error: unknown type name ‘__u32’
>   124 |  __u32 stx_dev_minor;
>       |  ^~~~~
> /usr/include/linux/stat.h:126:2: error: unknown type name ‘__u64’
>   126 |  __u64 __spare2[14]; /* Spare space for future expansion */
>       |  ^~~~~
> make[2]: *** [Makefile:130: syscalls/x86/modify_ldt.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/trinity_1.8-6_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 via email to