| 1 |
Am 07.09.2012 14:53, schrieb Tanstaafl: |
| 2 |
> On 2012-09-07 7:44 AM, Markos Chandras <hwoarang@g.o> wrote: |
| 3 |
>> On Fri, Sep 7, 2012 at 12:24 PM, Tanstaafl<tanstaafl@×××××××××××.org> |
| 4 |
>> wrote: |
| 5 |
>>> This has never happened to me before... |
| 6 |
>>> |
| 7 |
>>> Since when did a simple GCC upgrade *automatically* REMOVE my prior GCC |
| 8 |
>>> install??? |
| 9 |
>>> |
| 10 |
>>> I have *always* kept my prior GCC around for a while, if not until |
| 11 |
>>> the next |
| 12 |
>>> upgrade, just as something to fall back on if the current one breaks. |
| 13 |
>>> |
| 14 |
>>> I am NOT a happy camper. |
| 15 |
> |
| 16 |
>> This always happens if the gcc your are upgrading to is in the same |
| 17 |
>> slot as the previous one. |
| 18 |
> |
| 19 |
> Well, I've been managing this gentoo server since I installed it over 8 |
| 20 |
> years ago, and I don't *ever* recall a GCC upgrade removing my prior |
| 21 |
> version. |
| 22 |
> |
| 23 |
|
| 24 |
Well, then this simple little command should help you refresh your |
| 25 |
memory. It shows every install and uninstall of gcc on your system. |
| 26 |
|
| 27 |
With 8 years of emerge.log you are good to go |
| 28 |
|
| 29 |
genlop -ul | grep 'sys-devel/gcc-[0-9]' |
Archives