it seems that since we've added gcc-4 ebuilds to portage, people think we're supporting it ... we do and we dont ...
if you want something fixed for gcc-4, then create a good patch yourself, file a bug, and include the patch ... if the patch doesnt suck, we'll probably add it to portage ... if it does suck, we'll be inclined to inform you of such suckage and ask for a patch that doesnt suck quite as much (preferably a lot less) we're not about to start trying to reproduce the failure and tracking it down ourselves ... that step of support wont happen until gcc-4 is actually released so to recap: if you're a big enough boy to try to use gcc-4, you're a big enough boy to fix bugs yourself -mike -- [email protected] mailing list
