Your message dated Fri, 22 Nov 2013 23:17:22 +0100
with message-id <20131122221722.ga18...@raptor.chemicalconnection.dyndns.org>
and subject line Re: Bug #701346: quantlib: ftbfs with GCC-4.8
has caused the Debian Bug report #701346,
regarding quantlib: ftbfs with GCC-4.8
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.)
--
701346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:quantlib
Version: 1.2.1-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8
The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.
XXX
The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/quantlib_1.2.1-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.
To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev
The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.
[...]
Testing TQR eigenvector decomposition...
Testing tracing...
Testing transformed grid construction...
Testing Variance Gamma model for European options...
Testing variance option with integral Heston engine...
make[1]: *** wait: No child processes. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: *** wait: No child processes. Stop.
E: Caught signal 'Terminated': terminating immediately
make[3]: *** [check-TESTS] Terminated
make[2]: *** [check-am] Terminated
make: *** [test-stamp] Terminated
Build killed with signal TERM after 60 minutes of inactivity
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Build finished at 20130219-0129
Finished
ââââââââ
E: Build failure (dpkg-buildpackage died)
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Cleanup
â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Purging /«BUILDDIR»
Not cleaning session: cloned chroot in use
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Summary
â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Architecture: amd64
Build-Space: 637788
Build-Time: 8517
Distribution: unstable
Fail-Stage: build
Install-Time: 9
Job: quantlib_1.2.1-1
Package: quantlib
Package-Time: 8556
Source-Version: 1.2.1-1
Space: 637788
Status: attempted
Version: 1.2.1-1
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Finished at 20130219-0129
Build needed 02:22:36, 637788k disc space
DC-Status: Failed 8557.106605s
DC-Time-Estimation: 8557.106605 versus expected 5329 (r/m: 0.605762170200788 ;
m: 5329.0)
--- End Message ---
--- Begin Message ---
Hi,
On Sat, Feb 23, 2013 at 11:21:50AM +0000, Matthias Klose wrote:
> Package: src:quantlib
> Version: 1.2.1-1
> Severity: important
> Tags: sid jessie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-4.8
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
> severity of this report may be raised before the jessie release.
I appears newer versions do build fine now with gcc-4.8/g++-4.8 being
default:
https://buildd.debian.org/status/fetch.php?pkg=quantlib&arch=amd64&ver=1.3-2&stamp=1378126734
| quantlib 1.3-2 (amd64) 02 Sep 2013 10:15
[...]
|Toolchain package versions: binutils_2.23.52.20130828-1 dpkg-dev_1.17.1
g++-4.8_4.8.1-9 gcc-4.8_4.8.1-9 [...]
At least I don't see any work-arounds forcing gcc-4.7 either, so
closing. Please reopen if you believe this is still a problem.
Michael
--- End Message ---
