Source: frobtads
Version: 1:1.2.4-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Usertags: ftbfs-gcc-10

Hi,

frobtads started to FTBFS (at least on amd64) when GCC 10 was made
the default compiler:

[..]
g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.4/.  -DFROBTADS -DTC_TARGET_T3 
-DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
-I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads2 
-I/build/frobtads-1.2.4/./tads3 -I/build/frobtads
-1.2.4/./tads3/unix  -DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
-DT3_LIB_DIR=\"/usr/share/frobtads/tads3/lib\" 
-DT3_RES_DIR=\"/usr/share/frobtads/tads3/res\" -DT3_LOG_FILE=\"/tmp/frob.log\" 
-I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads2
 -I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads3 
-I/build/frobtads-1.2.4/./tads3/test -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/build/frobtads-1.2.4=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-strict-aliasi
ng -pthread -c -o tads3/charmap.o /build/frobtads-1.2.4/./tads3/charmap.cpp
In file included from /build/frobtads-1.2.4/./tads3/osifcnet.h:942,
                 from /build/frobtads-1.2.4/./tads3/vmdatasrc.h:23,
                 from /build/frobtads-1.2.4/./tads3/charmap.cpp:31:
/build/frobtads-1.2.4/./tads3/unix/osnetunix.h:222:20: error: missing '(' after 
"__has_builtin"
  222 | # if __has_builtin == 0
      |                    ^~
/build/frobtads-1.2.4/./tads3/unix/osnetunix.h:222:23: error: missing binary 
operator before token "0"
  222 | # if __has_builtin == 0
      |                       ^
make[2]: *** [Makefile:10276: tads3/charmap.o] Error 1
make[2]: Leaving directory '/build/frobtads-1.2.4/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:3854: all] Error 2
make[1]: Leaving directory '/build/frobtads-1.2.4/obj-x86_64-linux-gnu'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas

Reply via email to