Dale wrote: > Neil Bothwick wrote: > >> On Thu, 16 Apr 2009 16:12:16 -0500, Dale wrote: >> >> >> >>> I was using gcc 4.3 but switched back to gcc 4.1. I'm not a developer >>> and I don't feel right about filing a bug since I can't really tell them >>> what is broke but something is wrong somewhere. I have not syncd my >>> tree and it was a reinstall of the same version of packages. No config >>> files were updated or listed that needs to be updated either. >>> Basically, the only difference is the compiler. >>> >>> >> File a bug. It's like going to the doctor, you don't have to know what's >> wrong, just be able to describe the symptoms. >> >> >> >> > > I'm not sure what to even put. I do believe that gcc is causing > problems as far as the code it produces but I have no idea what could > cause it. > > I also have not changed my make.conf file. I only change it when they > add some new device or something like that. I think the last change I > made was to add kdeprefix. I can't see how it could be anything but gcc > but have no clue how it could be either. Looks like I wouldn't be the > only person to have this issue. > > I did notice that I can now compile a kernel. I have not had any errors > doing that with the old gcc. Maybe, just maybe I can upgrade to 2.6.29 now. > > Dale > > :-) :-) > >
I am now pretty sure this is a gcc issue. My emerge -ev world is almost done and while I slept my sound started working again. As far as I can tell, everything is working again. I think I'm going to wait a while before trying to upgrade gcc again. I still can't really say why gcc is messing up but on this system, it is. By the way, Seamonkey doesn't crash on websites or when I open emails anymore. Back to full time surfing. Thanks much. Dale :-) :-)
