See related bug report upstream [1] and same problem on f.g.o. [2] [1] https://sourceware.org/bugzilla/show_bug.cgi?id=23919 [2] https://forums.gentoo.org/viewtopic-t-1095306.html Other reference: https://bugzilla.redhat.com/show_bug.cgi?id=1678204 Reproducible: Always
That happens if you build something with 2.32 and then switch back to 2.31 ... (We only learned about that effect afterwards too.) Unfortunately, backporting stuff from 2.32 to 2.31 means that the effect will be the same with "fixed" 2.31 and "unfixed" 2.31 ... If you're on 2.32, stay on 2.32. If you're on 2.31, stay on 2.31. (Other distros have backported the patch to 2.31, but I'd rather keep things stable within the 2.31 series.)
(In reply to Andreas K. Hüttel from comment #1) > That happens if you build something with 2.32 and then switch back to 2.31 > ... In the case of the forum user the problem is caused by umasking >=dev-libs/elfutils-0.175 and not by switching the binutils version.
(In reply to Marco Genasci from comment #2) > (In reply to Andreas K. Hüttel from comment #1) > > That happens if you build something with 2.32 and then switch back to 2.31 > > ... > > In the case of the forum user the problem is caused by umasking > >=dev-libs/elfutils-0.175 and not by switching the binutils version. uh, ok, different but related issue then *** This bug has been marked as a duplicate of bug 671760 ***
