| 1 |
On 18/12/2014 09:45, meino.cramer@×××.de wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> on my embedded system I currently ran into a problem: |
| 5 |
> |
| 6 |
> As adviced after a greater world update I did |
| 7 |
> |
| 8 |
> emerge --depclean -vp |
| 9 |
> |
| 10 |
> beside other stuff sys-devel/gcc was shown as candidate |
| 11 |
> for removal. An old version was shown for removal and |
| 12 |
> a newer one was shown as preserved. |
| 13 |
> |
| 14 |
> I checked with eselect, whether the new version was selected |
| 15 |
> (it was), made a backup and started emerge --depclean -v. |
| 16 |
> |
| 17 |
> As soon it has removed gcc, a firework of error brightened |
| 18 |
> my terminal...beside other things the shell failed while |
| 19 |
> trying to access libgcc (if I had recognized that correctly...). |
| 20 |
> |
| 21 |
> Technically no problem: I stopped that, cleared the sdcard |
| 22 |
> and installed the backup...but what did I wrong here? |
| 23 |
> |
| 24 |
> What is the correct way to handle such things? |
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
That's a good question. My first thought was you could have c++ apps |
| 29 |
built against the old version of gcc, they will still use the old libs |
| 30 |
at runtime. |
| 31 |
|
| 32 |
depclean those, and you get fireworks like you got. |
| 33 |
|
| 34 |
Solution would seem to be emerge -e world with your choice of gcc |
| 35 |
enabled, then depclean the old versions. |
| 36 |
|
| 37 |
But, in 10+ years of using gentoo, I must admit that has never happened |
| 38 |
to me yet! |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Alan McKinnon |
| 43 |
alan.mckinnon@×××××.com |
Archives