| 1 |
I am one of the users experiencing the |
| 2 |
infinite rebuild of binutils |
| 3 |
bug. Today it took a turn I find worrisome |
| 4 |
|
| 5 |
To summarize for months now after every emerge I get |
| 6 |
|
| 7 |
!!! existing preserved libs: |
| 8 |
>>> package: sys-libs/binutils-libs-2.28.1 |
| 9 |
* - /usr/lib64/libbfd-2.25.1.so |
| 10 |
* used by |
| 11 |
/usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so |
| 12 |
(sys-devel/binutils-2.25.1-r1) |
| 13 |
Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 14 |
|
| 15 |
If if then |
| 16 |
emerge @preserved-rebuild |
| 17 |
it rebuilds binutils but I still get the above message. I have rebuilt |
| 18 |
it at least a dozen times in the past months. |
| 19 |
|
| 20 |
A solution was posted that involved making a quickpkg (I think), |
| 21 |
unmerging binutils, and then manually untaring (after the unmerge of |
| 22 |
binutils you can't simply remerge since ld is gone). |
| 23 |
|
| 24 |
This solution frightened me and I am living with always being told to run |
| 25 |
emerge @preserved-rebuild |
| 26 |
and actually doing that fruitless emerge about once a month. |
| 27 |
|
| 28 |
Today was different, I guess because binutils-lib was involved |
| 29 |
|
| 30 |
My "twice-weekly" |
| 31 |
emerge --update --changed-use --with-bdeps=y @world |
| 32 |
resulted in |
| 33 |
Calculating dependencies... done! |
| 34 |
[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" |
| 35 |
[ebuild U ] www-plugins/adobe-flash-27.0.0.130-r1 [27.0.0.130] |
| 36 |
[ebuild rR ] x11-libs/cairo-1.14.8 |
| 37 |
[ebuild r U ] sys-libs/binutils-libs-2.28.1 [2.28-r1] |
| 38 |
|
| 39 |
The following packages are causing rebuilds: |
| 40 |
|
| 41 |
(sys-libs/binutils-libs-2.28.1:0/2.28.1::gentoo, ebuild scheduled for merge) causes rebuilds for: |
| 42 |
(x11-libs/cairo-1.14.8:0/0::gentoo, ebuild scheduled for merge) |
| 43 |
|
| 44 |
When the emerge finished I received the usual |
| 45 |
|
| 46 |
!!! existing preserved libs: |
| 47 |
>>> package: sys-libs/binutils-libs-2.28.1 |
| 48 |
* - /usr/lib64/libbfd-2.25.1.so |
| 49 |
* 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) |
| 50 |
Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 51 |
|
| 52 |
But when I ran |
| 53 |
emerge @preserved-rebuild |
| 54 |
out came the following |
| 55 |
|
| 56 |
The following mask changes are necessary to proceed: |
| 57 |
(see "package.unmask" in the portage(5) man page for more details) |
| 58 |
# required by @preserved-rebuild (argument) |
| 59 |
# /var/portage/profiles/package.mask: |
| 60 |
# Michał Górny <mgorny@g.o>, Andreas K. Hüttel <dilfridge@g.o>, |
| 61 |
# Matthias Maier <tamiko@g.o> (21 May 2017) |
| 62 |
# These old versions of toolchain packages (binutils, gcc, glibc) are no |
| 63 |
# longer officially supported and are not suitable for general use. Using |
| 64 |
# these packages can result in build failures (and possible breakage) for |
| 65 |
# many packages, and may leave your system vulnerable to known security |
| 66 |
# exploits. |
| 67 |
# If you still use one of these old toolchain packages, please upgrade (and |
| 68 |
# switch the compiler / the binutils) ASAP. If you need them for a specific |
| 69 |
# (isolated) use case, feel free to unmask them on your system. |
| 70 |
=sys-devel/binutils-2.25.1-r1 |
| 71 |
|
| 72 |
NOTE: The --autounmask-keep-masks option will prevent emerge |
| 73 |
from creating package.unmask or ** keyword changes. |
| 74 |
|
| 75 |
Would you like to add these changes to your config files? [Yes/No] |
| 76 |
|
| 77 |
I said no since I don't want to unmask, but am not sure how to proceed |
| 78 |
|
| 79 |
Thanks in advance for any help. |
| 80 |
|
| 81 |
allan |
Archives