-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 22 January 2004 23:04, Frank J. Mattia wrote: > sorry, i was in a rush to leave for work this morning and now that im > rereading my message i can see that i was lacking in some clarity... so > heres more of a detailed explanation: > <single paragraph over 100 words - snipped> > > 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...
First read go and very very carefully read: http://www.gentoo.org/doc/en/handbook/handbook.xml?part=2&chap=2#doc_chap4 Once you've done that, _try_ downgrading gcc again unless your confident that you can fix this sort of thing by yourself every other time you emerge -u world. If it doesn't work, try linking libstdc++.so.5 to libstdc++.so.6 (or whatever the new one is called) and emerge -e world if that works. If not, you're pretty much on your own. Also realize that the most "bleeding-edge" thing you can do at the moment is to go with the 2.6 headers. Furthermore, they weren't actually required to use a 2.6 kernel. - -- Regards, Jason Stubbs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAD+U0osKAszmcBv4RAnNgAJ9owUAQ/n1668f2CcbAyiVrfSBKkACfdJ5p E84tJXtBVTWIYPw5uE+PV7Y= =kONY -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
