[Debian-med-packaging] Bug#759978: seqan: FTBFS: c++: error: unrecognized command line option '-strong'

Lucas Nussbaum lucas at lucas-nussbaum.net
Sat Aug 30 21:54:50 UTC 2014


Source: seqan
Version: 1.4.1+dfsg-1
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):
>  debian/rules build
> dh build
>    dh_testdir
>    dh_auto_configure
> 	mkdir -p obj-x86_64-linux-gnu
> 	cd obj-x86_64-linux-gnu
> 	cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
> -- The C compiler identification is GNU 4.9.1
> -- The CXX compiler identification is unknown
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- broken
> CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:54 (message):
>   The C++ compiler "/usr/bin/c++" is not able to compile a simple test
>   program.
> 
>   It fails with the following output:
> 
>    Change Dir: /«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp
> 
>   
> 
>   Run Build Command:/usr/bin/make "cmTryCompileExec625972386/fast"
> 
>   make[1]: Entering directory
>   '/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
>   /usr/bin/make -f CMakeFiles/cmTryCompileExec625972386.dir/build.make
>   CMakeFiles/cmTryCompileExec625972386.dir/build
> 
>   make[2]: Entering directory
>   '/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
>   /usr/bin/cmake -E cmake_progress_report
>   /«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CMakeFiles
>   1
> 
>   Building CXX object
>   CMakeFiles/cmTryCompileExec625972386.dir/testCXXCompiler.cxx.o
> 
>   /usr/bin/c++ -g -O2 -strong -Wformat -Werror=format-security
>   -D_FORTIFY_SOURCE=2 -o
>   CMakeFiles/cmTryCompileExec625972386.dir/testCXXCompiler.cxx.o -c
>   /«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
> 
> 
>   c++: error: unrecognized command line option '-strong'
> 
>   CMakeFiles/cmTryCompileExec625972386.dir/build.make:57: recipe for target
>   'CMakeFiles/cmTryCompileExec625972386.dir/testCXXCompiler.cxx.o' failed
> 
>   make[2]: Leaving directory
>   '/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
>   make[2]: ***
>   [CMakeFiles/cmTryCompileExec625972386.dir/testCXXCompiler.cxx.o] Error 1
> 
>   Makefile:114: recipe for target 'cmTryCompileExec625972386/fast' failed
> 
>   make[1]: *** [cmTryCompileExec625972386/fast] Error 2
> 
>   make[1]: Leaving directory
>   '/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
>   
> 
>   
> 
>   CMake will not be able to correctly generate this project.
> Call Stack (most recent call first):
>   CMakeLists.txt:9 (project)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
> See also "/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
> dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code 1
> make: *** [build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/seqan_1.4.1+dfsg-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. 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.



More information about the Debian-med-packaging mailing list