Your message dated Fri, 1 Aug 2014 15:46:44 +0200
with message-id <20140801134644.gd15...@an3as.eu>
and subject line Done with latest upload
has caused the Debian Bug report #746911,
regarding seqan: ftbfs with GCC-4.9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
746911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seqan
Version: 1.4.1-3
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of this report may be raised before the jessie release.

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/seqan_1.4.1-3_unstable_gcc49.log
The last lines of the build log are at the end of this report.

To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols
files.  For other C/C++ related build failures see the porting guide
at http://gcc.gnu.org/gcc-4.9/porting_to.html

[...]
 Skipped:     0
 Errors:      2
**************************************

      Start 40: test_test_index_stree_iterators
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: *** wait: No child processes.  Stop.
make[2]: *** [test] Terminated
make: *** [build-arch] Terminated
Build killed with signal TERM after 60 minutes of inactivity
────────────────────────────────────────────────────────────────────────────────
Build finished at 20140418-1604

Finished
────────

E: Build failure (dpkg-buildpackage died)

┌──────────────────────────────────────────────────────────────────────────────┐
│ Cleanup                                                                     
 │
└──────────────────────────────────────────────────────────────────────────────┘

Purging /«BUILDDIR»
Not cleaning session: cloned chroot in use

┌──────────────────────────────────────────────────────────────────────────────┐
│ Summary                                                                     
 │
└──────────────────────────────────────────────────────────────────────────────┘

Build Architecture: amd64
Build-Space: 3840412
Build-Time: 12447
Distribution: unstable
Fail-Stage: build
Host Architecture: amd64
Install-Time: 20
Job: seqan_1.4.1-3
Machine Architecture: amd64
Package: seqan
Package-Time: 12506
Source-Version: 1.4.1-3
Space: 3840412
Status: attempted
Version: 1.4.1-3
────────────────────────────────────────────────────────────────────────────────
Finished at 20140418-1604
Build needed 03:28:26, 3840412k disc space
DC-Status: Failed 12508.516633953s
DC-Time-Estimation: 12508.516633953 versus expected 1551 (r/m: 7.06480762988588 
; m: 1551.0)

--- End Message ---
--- Begin Message ---
Hi,

seqan was compiled successfully now with gcc-4.9 but this was not mentioned in 
d/changelog.

-- 
http://fam-tille.de

--- End Message ---

Reply via email to