On 2020-11-19 08:36, Roderick wrote: > > broken gcc is the old gcc, the one of the package is installed as egcc. > > Do only I have a broken gcc? > > R. > > On Thu, 19 Nov 2020, Roderick wrote: > >> >> After upgrading, I still have gcc, but no package gcc. >> >> I get the above error. I get it also after installing gcc, and also after >> deinstalling it, making "pkg_delete -a" and reinstalling. >> >> Any hint, what can I do?
You have provided almost no info to go on. Upgraded from what to what? On what platform? What process did you use? I'm not even sure what you are wanting to do -- run base gcc? Run a package gcc? I think it is very safe to say you made an error somewhere, probably in an upgrade process. Not necessarily in your most recent upgrade, it may just be a problem than finally came home to roost. Most likely (since I've done it, I'm going to assume you did), you skipped some important step in upgradeXX.html that wasn't unimportant. You may have even got away with it for a few upgrades since. Worst case, unload all pacakges, then go through the /usr, /bin and /bin directories looking for files older than your current install, and removing them (most of them aren't bad. But something isn't right). Then do another upgrade to whatever you want to be running, because you probably just blew away something incorrectly. Finally, reinstall packages you want. And to be clear -- I'm NOT advocating deleting old files for giggles or as any kind of routine activity as part of an upgrade. But on a screwed up system, the hunt for old files often reveals what is actually going on. (in my case, I recently found my userland and kernel were over a year out of sync on a machine I only use occasionally, due to unsupervised upgrades and not looking at the results. I had not properly removed the /var/tmp directory however long ago that was, and base unpacks a symlink in /var/tmp to /tmp, that failed, tar bailed and much of baseXX.tgz was never unpacked. I'm really surprised this machine was as functional as it was.) Nick.
