Hi! On 12/02/2013 01:14 PM, Matthias Klose wrote: > Afaics, the situation didn't change. There is nobody committing to work on the > toolchain for these architectures. At least for release architectures the > alternative is to drop the port unless somebody wants to maintain the > toolchain > for this port. This is the current status, please correct me if I'm wrong.
> - powerpcspe, no feedback, CCing Roland Stigge. >> Please resume considering to change using unified version of gcc, >> because FTBFS of many packages occur by e.g. c++11 >> on ports which stayed using gcc-4.6 and g++-4.6, >> ia64, powerpc, s390x, sparc, alpha, powerpcspe, ppc64, sh4. Thanks for the note! I'm actually currently working on gcc-4.8 for powerpcspe. gcc-4.7 and gcc-4.8 on powerpcspe build well, except they both don't have "--with-long-double-128" activated currently (in contrast to the current default gcc-4.6 and on powerpc). --with-long-double-128 can be activated on gcc-4.7 right away. I'm filing a wishlist bug for this. For gcc-4.8, I'm still looking for a solution. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57386 I'm proposing to have gcc-4.7 as default for now with activated --with-long-double-128. As soon as GCC's #57386 is solved, gcc-4.8 can be used without problems. Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org