Matthias Klose wrote: > The point of reassigning the report to an unknown package is to ask, > if it's time to drop m68k from the release architectures or just set > the severity of all m68k reports to wishlist. There's currently nobody > interested in forwarding m68k related bug reports upstream and testing > m68k compiler versions. There are at least six more unhandled m68k > reports.
m68k isn't fully maintained upstream at GCC. The listed maintainers are Jeff Law (who is really mostly busy doing other things), and Andreas Schwab (who does his best, but is not really able to keep up with the high demands of the port by himself). It has a lot of code which needs to be updated to current GCC standards and is therefore notoriously irritating to debug. I doubt that it's reasonable to maintain a port to m68k under these conditions. -- Nathanael Nerode <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
