Source: dosbox-x
Version: 2025.02.01+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20250416 ftbfs-trixie

Hi,

During a rebuild of all packages in testing (trixie), your package failed
to build on armhf.


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../../src/hardware -I../..  -I../../../include 
> -I../../../src/aviwriter -I../../../src/hardware/snd_pc98/sound 
> -I../../../src/hardware/snd_pc98/common 
> -I../../../src/hardware/snd_pc98/generic 
> -I../../../src/hardware/snd_pc98/sound/getsnd 
> -I../../../src/hardware/snd_pc98/x11 -I../../../src/hardware/snd_pc98/cbus 
> -I../../../src -Wno-int-to-void-pointer-cast   -Wno-address-of-packed-member  
>  -Wno-format-zero-length   -Wno-missing-field-initializers   
> -Wno-strict-aliasing   -Wno-implicit-fallthrough   
> -Wno-deprecated-declarations   -Wnon-virtual-dtor   -Wsuggest-override   
> -Wconversion-null   -Wsign-promo   -Wlogical-op   
> -Wno-error=incompatible-pointer-types   -Wno-error=format-security   
> -pedantic   -Wunused   -Wextra   -Wall  -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/SDL2 -D_REENTRANT   
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg 
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg/vs/sdlnet/linux-host/include
>  
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg/vs/sdlnet/linux-host/include/SDL
>  -I/usr/include/freetype2 -I/usr/include/libpng16  -DLIBSLIRP_STATIC 
> -I/usr/include/slirp -I/usr/include/glib-2.0 
> -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/sysprof-6 
> -pthread   -g -Werror=implicit-function-declaration 
> -ffile-prefix-map=/build/reproducible-path/dosbox-x-2025.02.01+dfsg=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -std=gnu11  -O2  
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg 
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg/vs/sdlnet/linux-host/include
>  
> -I/build/reproducible-path/dosbox-x-2025.02.01+dfsg/vs/sdlnet/linux-host/include/SDL
>  -I/usr/include/freetype2 -I/usr/include/libpng16  -DLIBSLIRP_STATIC 
> -I/usr/include/slirp -I/usr/include/glib-2.0 
> -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/sysprof-6 
> -pthread  -c -o esfmu/esfm_registers.o 
> ../../../src/hardware/esfmu/esfm_registers.c
> cc1: warning: command-line option ‘-Wnon-virtual-dtor’ is valid for 
> C++/ObjC++ but not for C
> cc1: warning: command-line option ‘-Wsuggest-override’ is valid for 
> C++/ObjC++ but not for C
> cc1: warning: command-line option ‘-Wconversion-null’ is valid for C++/ObjC++ 
> but not for C
> cc1: warning: command-line option ‘-Wsign-promo’ is valid for C++/ObjC++ but 
> not for C
> In function ‘ESFM_process_feedback’,
>     inlined from ‘ESFM_generate’ at ../../../src/hardware/esfmu/esfm.c:2222:2:
> ../../../src/hardware/esfmu/esfm.c:1915:25: error: ‘asm’ operand has 
> impossible constraints or there are not enough registers
>  1915 |                         asm (
>       |                         ^~~
> At top level:
> cc1: note: unrecognized command-line option ‘-Wno-int-to-void-pointer-cast’ 
> may have been intended to silence earlier diagnostics
> make[6]: *** [Makefile:815: esfmu/esfm.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2025/04/16/dosbox-x_2025.02.01+dfsg-1_testing-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250416;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250416&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to