On Sat, Jul 12, 2014 at 00:08:28 +0900, Osamu Aoki wrote: > But this seems toi be a bug porter amd GCC maintainer has to address. > If they can not, we should drop armel from Debian.
I would rather drop any package which does use c++11 features without any reflection. The c++11 status in GCC (and any compiler using libstdc++) is still marked as experimental [1]. See [2] for further updates on the c++11 status in 4.9. Therefore the package maintainers have to accommodate for that, if the upstream projects don't do it. This is the status for jessie. The GCC maintainers did address the issue [3], and it can be fixed just by bumping the cpu requirements to armv7 (as done for sparc/v9 in the past, to keep the port alive a bit longer). However this shouldn't be done before the jessie release. Debian generally is not able to maintain the toolchain alone if upstream doesn't support it anymore. Examples from the past are the s390, sparc, ia64, and probably other ports on ports.debian.org. I pinged several Debian ARM porters about the issue, but didn't get any feedback yet. I wouldn't mind making armel a port for jessie+1 if issues like these cannot be addressed. Matthias [1] https://gcc.gnu.org/projects/cxx0x.html [2] https://gcc.gnu.org/gcc-4.9/changes.html [3] https://gcc.gnu.org/ml/gcc/2014-07/msg00000.html -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c12363.70...@debian.org
