On 18/12/2014 09:45, [email protected] wrote: > Hi, > > on my embedded system I currently ran into a problem: > > As adviced after a greater world update I did > > emerge --depclean -vp > > beside other stuff sys-devel/gcc was shown as candidate > for removal. An old version was shown for removal and > a newer one was shown as preserved. > > I checked with eselect, whether the new version was selected > (it was), made a backup and started emerge --depclean -v. > > As soon it has removed gcc, a firework of error brightened > my terminal...beside other things the shell failed while > trying to access libgcc (if I had recognized that correctly...). > > Technically no problem: I stopped that, cleared the sdcard > and installed the backup...but what did I wrong here? > > What is the correct way to handle such things?
That's a good question. My first thought was you could have c++ apps built against the old version of gcc, they will still use the old libs at runtime. depclean those, and you get fireworks like you got. Solution would seem to be emerge -e world with your choice of gcc enabled, then depclean the old versions. But, in 10+ years of using gentoo, I must admit that has never happened to me yet! -- Alan McKinnon [email protected]
