Source: instead
Version: 3.2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/cc 
> -DGAMES_PATH=\"/usr/share/games/instead/games/\" 
> -DICON_PATH=\"/usr/share/pixmaps/\" 
> -DLANG_PATH=\"/usr/share/games/instead/lang/\" 
> -DSTEAD_PATH=\"/usr/share/games/instead/stead/\" 
> -DTHEMES_PATH=\"/usr/share/games/instead/themes/\" -DVERSION=\"3.2.1\" 
> -D_HAVE_ICONV -D_USE_BROWSE -D_USE_GTK -D_USE_SDL -D_USE_UNPACK -Dunix 
> -I/usr/include/lua5.1 -I/usr/include/x86_64-linux-gnu/SDL2 
> -I/usr/include/SDL2 -I/usr/include/freetype2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include  -g -O2 
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wall -Wextra 
> -Wno-unused-parameter -o CMakeFiles/sdl-instead.dir/game.c.o   -c 
> /<<PKGBUILDDIR>>/src/game.c
> In file included from /<<PKGBUILDDIR>>/src/SDL_anigif.h:59,
>                  from /<<PKGBUILDDIR>>/src/SDL_anigif.c:24:
> /usr/include/x86_64-linux-gnu/SDL2/close_code.h:30:2: error: #error 
> close_code.h included without matching begin_code.h
>    30 | #error close_code.h included without matching begin_code.h
>       |  ^~~~~
> make[3]: *** [src/CMakeFiles/sdl-instead.dir/build.make:66: 
> src/CMakeFiles/sdl-instead.dir/SDL_anigif.c.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/instead_3.2.1-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 via email to