Bug#759853: dragonegg: FTBFS: g++-4.8: error: unrecognized command line option '-fstack-protector-strong'

[Lucas Nussbaum]

Source: dragonegg
Version: 3.4-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140830 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):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> gcc-4.8 --version > /dev/null
> /usr/lib/llvm-3.4/bin/llvm-config --version > /dev/null
> Compiling utils/TargetInfo.cpp
> g++-4.8 -c \
> -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\"3.4.2\" -DTARGET_TRIPLE=\"x86_64-linux-gnu\" -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/utils/TargetInfo.cpp
> g++-4.8: error: unrecognized command line option '-fstack-protector-strong'
> make[1]: *** [TargetInfo.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/dragonegg_3.4-2_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. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.