> gcc3.0 is in contrib and wasn't ready when mdk8.0 got out of the box (needless > to says that using a new compiler means rebuilding all packages (3-4 days with > rpm-rebuilder) and _testing_) The only package that I know has problems with 2.96 is LAME. It builds, but has runtime errors in the release build. I switched to the 3.0 compiler and the problems went away.
- [Cooker] Why gcc 2.96 and not 3.0? Chris Mumford
- Re: [Cooker] Why gcc 2.96 and not 3.0? Thierry Vignaud
- Re: [Cooker] Why gcc 2.96 and not 3.0? Chris Mumford
- Re: [Cooker] Why gcc 2.96 and not 3.0? J . A . Magallon
- Re: [Cooker] Why gcc 2.96 and not 3.... Maks Orlovich
- Re: [Cooker] Why gcc 2.96 and not 3.... Guillaume Cottenceau
- Re: [Cooker] Why gcc 2.96 and n... J . A . Magallon
- Re: [Cooker] Why gcc 2.96 a... Gwenole Beauchesne
- Re: [Cooker] Why gcc 2.96 and not 3.0? Christian Zoffoli
- Re: [Cooker] Why gcc 2.96 and not 3.0? Thierry Vignaud
- Re: [Cooker] Why gcc 2.96 and not 3.... Blue Lizard
- Re: [Cooker] Why gcc 2.96 and n... Guillaume Cottenceau
- Re: [Cooker] Why gcc 2.96 and not 3.0? Guillaume Cottenceau
