For me the main problem was an error in 'eselect-compiler' ebuild file. After unmerging the package,
/etc/env.d/05compiler file was not deleted. As a result, enviroment variables were invalid. After deleting the file (and 'env-update' and 'source /etc/profile') switching to 4.1.1 was seamless (in accordance with official guide). ======= On Friday 08 September 2006 18:24, Grant wrote: ======= > I am leaving my office in a moment to put the 2006.1 disk in a server to > start a fresh build (it's a standby server and I can afford to have it > off line for a day or 2) specifically to avoid having to do the gcc4 > upgrade. Ive done one so far and it took me 5 days and nearly cost me > my laptop -- and I followed the gentoo guide specifically. There has > GOT to be a better way. Sadly I cant take each of my servers offline to > do upgrade them this way -- some I will have to risk on the GCC upgrade, > but for now im avoiding it like the plague. > > Tim I've followed the GCC upgrade guide before without problems, but now I'm scared. Is all the trouble because of how Gentoo works or how GCC works? What is the trouble like? Packages that won't compile, or different things breaking in the system? - Grant -- gentoo-user@gentoo.org mailing list
