James wrote: > Dale <rdalek1967 <at> gmail.com> writes: > > > >> You can compile Seamonkey with the old version but it COULD cause >> problems with the libraries it depends on. It may work fine tho. It is >> worth a try. Just select the old compiler and re-emerge seamonkey. >> > > Done > Seamonkey works now. > > >> Also worth noting, I to tried the new gcc and ran into a lot of >> problems. Not all of them were Seamonkey but it gave me problems as >> well. Another person had trouble with mythtv. You are not alone here. >> > > OK, so I'll file a bug report, on gcc-4.3.2. > > > A runtine update (not certain when) changed gcc to 4.3.2. > So Should I recompile everything? Discover what get compiled > with 4.3.2 and recompile it (how?) ? > > Or just leave it like it is, som 4.3.2 and some 4.1.2 binaries > mixed, until the devs figure things out? > > > guidance? > > > James > > >
Well, I had so many problems with other things that I went back to gcc-4.1 and did a emerge -e world. There was a lot of buggy and weird things going on and I wanted to be stable. I couldn't compile a kernel with gcc 4.3. Seamonkey would crash a lot. There were other things but my memory is not like a elephant. If everything is working fine, I would leave it like it is. Just keep in mind that it is compiled with the old gcc in case something funny starts to happen. Glad that you are running again tho. Dale :-) :-)
