Source: memtest86+
Version: 5.01-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
>  ^~~~~~
> gcc -Wall -march=i486 -m32 -O0 -fomit-frame-pointer -fno-builtin 
> -ffreestanding -fPIC  -fno-stack-protector -fgnu89-inline   -c -o vmem.o 
> vmem.c
> gcc -c -Wall -march=i486 -m32 -O3 -fomit-frame-pointer -fno-builtin 
> -ffreestanding random.c
> gcc -Wall -march=i486 -m32 -O0 -fomit-frame-pointer -fno-builtin 
> -ffreestanding -fPIC  -fno-stack-protector -fgnu89-inline   -c -o multiboot.o 
> multiboot.c
> ld -z max-page-size=0x1000 --warn-constructors --warn-common -static -T 
> memtest_shared.lds \
>  -o memtest_shared head.o reloc.o main.o test.o init.o lib.o patn.o 
> screen_buffer.o config.o cpuid.o linuxbios.o pci.o memsize.o spd.o error.o 
> dmi.o controller.o smp.o vmem.o random.o multiboot.o && \
> ld -z max-page-size=0x1000 -shared -Bsymbolic -T memtest_shared.lds -o 
> memtest_shared head.o reloc.o main.o test.o init.o lib.o patn.o 
> screen_buffer.o config.o cpuid.o linuxbios.o pci.o memsize.o spd.o error.o 
> dmi.o controller.o smp.o vmem.o random.o multiboot.o
> objcopy -O binary memtest_shared memtest_shared.bin
> gcc -E -traditional bootsect.S -o bootsect.s
> as -32   -o bootsect.o bootsect.s
> gcc -E -traditional setup.S -o setup.s
> as -32   -o setup.o setup.s
> ld -z max-page-size=0x1000 -T memtest.bin.lds bootsect.o setup.o -b binary \
> memtest_shared.bin -o memtest.bin
> ld -z max-page-size=0x1000 -s -T memtest.lds -b binary memtest_shared.bin -o 
> memtest
> Makefile:42: recipe for target 'memtest' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/memtest86+_5.01-3_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