last week i had started my trip to the bleeding edge pretty gently. i had a 2.6.0 kernel and decided to get the linux-headers to match. got the headers, added nptl to my use flags, recompiled kernel, then glibc. all is well. nptl works. i passed on recompiling my whole system just yet because of the problems with X and svgalib. moving to the end of last week i started using the 2.6.0-mm series. impressed with the mm branch this week i moved to the 2.6.1-mm line. note, since the first time i recompiled glibc, i have not done it since. yesterday i noticed a glibc upgrade so i decided to go for it. however before the build process started i got an error about the kernel or headers or something being incompatible with nptl. from here i assumed that it was because my headers didnt match my kernel. to my dimay (or maybe i just dont know something that everyone else does) i could not find any 2.6.1 linux-headers. after some toying around i decided to go "~x86" and started upgrading packages... first portage... then gentoolkit.. then binutils... then gcc.. BAM... after gcc upgraded to 3.3.something (the lastest inportage as of yesterday).. most apps that i open say they cant find libstdc++.so.5 .... which isnt suprising because it doesnt exist anymore...
so is there a sane way for me to go about fixing this problem or do i just never upgrade gcc? or is there a certain way of upgrading gcc as to not break things...
thanks again, Frank
whats the standard way of upgrading gcc? i just started using ~x86 last nite and upgrading gcc completed - but is now throwing more errors on libstdc++.so.5
even emerge throws errors on it. so i cant emerge anything else. any idea whats going on? im using a 2.6.1-mm5 kernel with 2.6.0 linux-headers (because 2.6.1 headers arent out in portage apparently) with NPTL in glibc (compiled when my kernel matched my headers, last week).
thanks.
-- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
