Bug#727621: armel: std::future appears to be broken?
Package: g++-4.8
Version: 4.8.1-10
Severity: normal
Hello, thank you for maintaining GCC.
When I tried to compile cupt 2.6.x in unstable/experimental, an armel
build (out of all) failed. This unfortunately blocks cupt's migration to
testing.
unstable, used g++ 4.8 - [1]
unstable, used g++ 4.6 - [2]
experimental, used g++ 4.6 - [3]
Errors were a bit different between 4.6 and 4.8, but both didn't like
something about std::future. Builds on other architectures, including
armhf, went fine.
[1]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.3&stamp=1382566839
[2]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.2&stamp=1381599864
[3]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.1&stamp=1381587241
-- System Information:
Debian Release: 6.0.5
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages g++-4.8 depends on:
ii gcc-4.8 4.8.1-10
ii gcc-4.8-base 4.8.1-10
ii libc6 2.17-3
ii libcloog-isl4 0.18.0-2
ii libgmp10 2:5.0.5+dfsg-2
ii libisl10 0.11.2-1
ii libmpc3 1.0.1-1
ii libmpfr4 3.1.1-2
ii libstdc++-4.8-dev 4.8.1-10
ii zlib1g 1:1.2.7.dfsg-13
g++-4.8 recommends no packages.
Versions of packages g++-4.8 suggests:
pn g++-4.8-multilib <none>
pn gcc-4.8-doc <none>
pn libstdc++6-4.8-dbg <none>
-- no debconf information
Reply to: