Andrew Haley wrote: > Gary Benson writes: > > The obvious place is in gcc itself (and aot-compile-rpm itself > > could either go there or in rpm) but that would mean being tied > > to gcc's necessarily slow release cycle. > > gcc doesn't seem to be having a very slow release cycle at the > moment: we've seen GCC 4.0.2 in September, GCC 4.0.1 in July and > GCC 4.0.0 in April. I meant the rpm. At the moment I can change a-c-r and push the packages out myself: I can't do that for gcc, and I'd have to wait the two weeks to a month until the next gcc rpm was built. Cheers, Gary
