# file /usr/lib64/libqb.so /usr/lib64/libqb.so: ASCII text This breaks linking in other software, e.g.: [..] /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: warning: //usr/lib64/libqb.so contains output sections; did you forget -T? /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find /var/tmp/portage/sys-cluster/libqb-1.0.5/work/libqb-1.0.5/lib/qblog_script.ld: No such file or directory collect2: error: ld returned 1 exit status [..] For a workaround, I tried: # sudo rm /usr/lib64/libqb.so # sudo ln -s libqb.so.0 /usr/lib64/libqb.so Still gets me the qblog_script.ld error quoted above.
sys-cluster/libqb-1.0.1 does not seem to have this problem.
i think this is problem which prevents me to emerge sys-cluster/pacemaker.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7e5e69bf829c1d7972ad069d415f24937417ffa4 commit 7e5e69bf829c1d7972ad069d415f24937417ffa4 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2020-01-02 21:38:41 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2020-01-02 21:44:12 +0000 sys-cluster/libqb: 1.9.0 Bug: https://bugs.gentoo.org/704514 Bug: https://bugs.gentoo.org/699860 Signed-off-by: Sebastian Pipping <sping@gentoo.org> Package-Manager: Portage-2.3.84, Repoman-2.3.20 sys-cluster/libqb/Manifest | 1 + sys-cluster/libqb/libqb-1.9.0.ebuild | 62 ++++++++++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+)
For the record, 1.9.0 does not have this problem and has CVE-2019-12779 fixed (in contrast to 1.0.1). What should we do about 1.0.5?
with libqb-1.9 emerged, emerge of pacemaker is now correct. maybe to declare 1.9 stable? (and remove 1.5 from portage)