Hi there. Quite a few RC bugs against packages exist that refer to #317475 as possible cause for FTBFS on m68k. AFAIK this could be fixed with gcc 4.0.2. How should this be tested? Will you just requeue them or should we do manual builds on crest? Or is the bug known to not be fixed at all?
Here a list of affected packages (all in state "failed" currently unless otherwise noted): pyid3lib #328452 pngwriter #328456 smart #328457 pyflac #326904 pyopenal #325563 python-extclass #323389 soya #325564 -> this has even been build successfully umfpack #323387 uqwk #329089 xjdic #327112 Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
