Source: refind Version: 0.10.3-1 Severity: serious Tags: stretch sid User: [email protected] Usertags: qa-ftbfs-20160714 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/gcc -Os -fno-strict-aliasing -fno-stack-protector -fshort-wchar > -Wall -DEFIX64 -DEFI_FUNCTION_WRAPPER -m64 -mno-red-zone -fpic > -I/usr/include/efi -I/usr/include/efi/x86_64 -I/usr/include/efi/protocol > -I../include -I../refind -I../libeg -I../mok -DFSTYPE=ext2 -I. > "-DEFIAPI=__attribute__((ms_abi))" \ > -D__MAKEWITH_GNUEFI -DREFIND_VERSION='L"0.10.3"' -c fsw_efi.c -o > fsw_efi.o > In file included from fsw_efi.c:45:0: > edk2/ComponentName.h:55:23: error: conflicting types for > 'EFI_COMPONENT_NAME_GET_DRIVER_NAME' > (EFI_FUNCTION EFIAPI *EFI_COMPONENT_NAME_GET_DRIVER_NAME)( > ^ > In file included from /usr/include/efi/efi.h:39:0, > from fsw_efi_base.h:46, > from fsw_core.h:45, > from fsw_efi.h:41, > from fsw_efi.c:41: > /usr/include/efi/efiprot.h:878:10: note: previous declaration of > 'EFI_COMPONENT_NAME_GET_DRIVER_NAME' was here > (EFIAPI *EFI_COMPONENT_NAME_GET_DRIVER_NAME) ( > ^ > In file included from fsw_efi.c:45:0: > edk2/ComponentName.h:104:23: error: conflicting types for > 'EFI_COMPONENT_NAME_GET_CONTROLLER_NAME' > (EFI_FUNCTION EFIAPI *EFI_COMPONENT_NAME_GET_CONTROLLER_NAME)( > ^ > In file included from /usr/include/efi/efi.h:39:0, > from fsw_efi_base.h:46, > from fsw_core.h:45, > from fsw_efi.h:41, > from fsw_efi.c:41: > /usr/include/efi/efiprot.h:885:10: note: previous declaration of > 'EFI_COMPONENT_NAME_GET_CONTROLLER_NAME' was here > (EFIAPI *EFI_COMPONENT_NAME_GET_CONTROLLER_NAME) ( > ^ > make[4]: *** [fsw_efi.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/14/refind_0.10.3-1_unstable_gcc5.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.
