I am one of the users experiencing the
infinite rebuild of binutils
bug. Today it took a turn I find worrisome
To summarize for months now after every emerge I get
!!! existing preserved libs:
>>> package: sys-libs/binutils-libs-2.28.1
* - /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
If if then
emerge @preserved-rebuild
it rebuilds binutils but I still get the above message. I have rebuilt
it at least a dozen times in the past months.
A solution was posted that involved making a quickpkg (I think),
unmerging binutils, and then manually untaring (after the unmerge of
binutils you can't simply remerge since ld is gone).
This solution frightened me and I am living with always being told to run
emerge @preserved-rebuild
and actually doing that fruitless emerge about once a month.
Today was different, I guess because binutils-lib was involved
My "twice-weekly"
emerge --update --changed-use --with-bdeps=y @world
resulted in
Calculating dependencies... done!
[ebuild NS ] sys-kernel/gentoo-sources-4.12.12 [3.10.3-r1, 3.11.0, 3.12.13,
3.18.11, 3.18.12, 4.0.5, 4.0.9, 4.1.12, 4.1.15-r1, 4.4.6, 4.4.21, 4.4.26,
4.4.39, 4.9.6-r1, 4.9.16, 4.9.34, 4.12.5] USE="-build -experimental -symlink"
[ebuild U ] www-plugins/adobe-flash-27.0.0.130-r1 [27.0.0.130]
[ebuild rR ] x11-libs/cairo-1.14.8
[ebuild r U ] sys-libs/binutils-libs-2.28.1 [2.28-r1]
The following packages are causing rebuilds:
(sys-libs/binutils-libs-2.28.1:0/2.28.1::gentoo, ebuild scheduled for merge)
causes rebuilds for:
(x11-libs/cairo-1.14.8:0/0::gentoo, ebuild scheduled for merge)
When the emerge finished I received the usual
!!! existing preserved libs:
>>> package: sys-libs/binutils-libs-2.28.1
* - /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
But when I ran
emerge @preserved-rebuild
out came the following
The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by @preserved-rebuild (argument)
# /var/portage/profiles/package.mask:
# Michał Górny <[email protected]>, Andreas K. Hüttel <[email protected]>,
# Matthias Maier <[email protected]> (21 May 2017)
# These old versions of toolchain packages (binutils, gcc, glibc) are no
# longer officially supported and are not suitable for general use. Using
# these packages can result in build failures (and possible breakage) for
# many packages, and may leave your system vulnerable to known security
# exploits.
# If you still use one of these old toolchain packages, please upgrade (and
# switch the compiler / the binutils) ASAP. If you need them for a specific
# (isolated) use case, feel free to unmask them on your system.
=sys-devel/binutils-2.25.1-r1
NOTE: The --autounmask-keep-masks option will prevent emerge
from creating package.unmask or ** keyword changes.
Would you like to add these changes to your config files? [Yes/No]
I said no since I don't want to unmask, but am not sure how to proceed
Thanks in advance for any help.
allan
