List, I figure upgrading to GCC 4.1.1 from 3.4.5 wouldn't be such a pain, right? WRONG. So far I've had just about every problem under the sun, mostly in the form of filesize errors.... which I wouldn't think would be related to GCC, but then again:
app-admin/perl-cleaner x11-proto/xextproto x11-proto/xcmiscproto-1.1.2 These packages quit on me after telling me that the reported filesize by the ebuild wasn't equal to the downloaded filesize. This only happened with gcc-config 6 (4.1.1). When I switched back to 3.4.5, emerge -e world was flawless. Very odd. I also had several packages quit on me related to gnome and GTK. Complaints were usually related to GTK being compiled and installed, however would not run. If these are the type of problems we're going to see with 4.1.1, I would have to vote that it stay masked. "Testing" isn't even the word for this so far. I had to revert back to my 3.4.5 gcc and re-emerge system after having too many errors to warrant continuing. Maybe I'll check back in a while, or if someone has a solution, I'd be more than willing to listen. -- Jason Weisberger [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
