| 1 |
On 14/03/2017 17:45, Grant Edwards wrote: |
| 2 |
> After I do an update, I get this message: |
| 3 |
> |
| 4 |
> !!! existing preserved libs: |
| 5 |
> >>> package: sys-libs/binutils-libs-2.27 |
| 6 |
> * - /usr/lib64/libbfd-2.25.1.so |
| 7 |
> * used by /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so (sys-devel/binutils-2.25.1-r1) |
| 8 |
> Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 9 |
> |
| 10 |
> When I do an 'emerge @preserved-rebuild', it re-builds |
| 11 |
> binutils-2.25.1, and then shows the same warning again. |
| 12 |
> |
| 13 |
> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and |
| 14 |
> logging out/in between. Still, I always get the same preserved-libs |
| 15 |
> warning. |
| 16 |
> |
| 17 |
> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1 |
| 18 |
> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't |
| 19 |
> help. |
| 20 |
> |
| 21 |
|
| 22 |
I've run into similar things a few times and never really got to the |
| 23 |
bottom of any of them and ldd wasn't very useful either. |
| 24 |
|
| 25 |
How I have got around it in the past is to stop rebuilding, that just |
| 26 |
keeps the crazy loop going as each time the new thing doesn't like the |
| 27 |
existing thing. So I emerge -C the offending package and the |
| 28 |
dependencies, then emerge both back in so they start from scratch. |
| 29 |
|
| 30 |
But in this case, removing binutils might be problematic, that's where |
| 31 |
your elf tools and linker come from. A workaround comes to mind: |
| 32 |
|
| 33 |
- quickpkg both packages |
| 34 |
- emerge -C both packages |
| 35 |
- manually untar both quickpkg archives to their original location. Now |
| 36 |
you have all your tools back, without the package metadata to confuse |
| 37 |
portage |
| 38 |
- emerge both packages, ignoring the expected file collision errors. |
| 39 |
|
| 40 |
-- |
| 41 |
Alan McKinnon |
| 42 |
alan.mckinnon@×××××.com |
Archives