Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Willie M]

On 03/14/2017 09:52 AM, Alan McKinnon wrote:
> On 14/03/2017 17:45, Grant Edwards wrote:
>> After I do an update, I get this message:
>>
>>   !!! existing preserved libs:
>>   >>> package: sys-libs/binutils-libs-2.27
>>    *  - /usr/lib64/libbfd-2.25.1.so
>>    *      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)
>>   Use emerge @preserved-rebuild to rebuild packages using these libraries
>>
>> When I do an 'emerge @preserved-rebuild', it re-builds
>> binutils-2.25.1, and then shows the same warning again.
>>
>> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
>> logging out/in between.  Still, I always get the same preserved-libs
>> warning.
>>
>> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
>> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
>> help.
>>
> I've run into similar things a few times and never really got to the
> bottom of any of them and ldd wasn't very useful either.
>
> How I have got around it in the past is to stop rebuilding, that just
> keeps the crazy loop going as each time the new thing doesn't like the
> existing thing. So I emerge -C the offending package and the
> dependencies, then emerge both back in so they start from scratch.
>
> But in this case, removing binutils might be problematic, that's where
> your elf tools and linker come from. A workaround comes to mind:
>
> - quickpkg both packages
> - emerge -C both packages
> - manually untar both quickpkg archives to their original location. Now
> you have all your tools back, without the package metadata to confuse
> portage
> - emerge both packages, ignoring the expected file collision errors.
>

Way better idea than I had with just a warning.

-- 

Willie L Matthews
matthews.willie80@×××××.com
702-659-9966