From: 蔺小渊 <shenxiaogll@163.com>
To: overseers@sourceware.org
Subject: New Account apply
Date: Wed, 6 Apr 2022 15:03:16 +0800 [thread overview]
Message-ID: <A1261E8E-8819-4C0A-A594-54A68E5B62C2@163.com> (raw)
Hi，I want to report a bug of binutils.
After backporting some patches from binutils-2.37 to binutils-2.34 to solve CVE-2021-20197, we find when compiling parallelly，the generated .so file lose some linked so.
Expected behavior:
[root@localhost ~]# ldd libcwall_ce.so
linux-vdso.so.1 (0x00007fff1ef73000)
libachk.so => /usr/lib64/libachk.so (0x00007f0377c98000)
libdefault.so => not found
liblpcc.so => not found
libccellprotein.so => not found
......
libc.so.6 => /usr/lib64/libc.so (0x00007f0377ade000)
Unexpected behavior:
[root@localhost ~]# ldd libcwall_ce.so
linux-vdso.so.1 (0x00007fff1ef73000)
libachk.so => /usr/lib64/libachk.so (0x00007f0377c98000)
libdefault.so => not found
liblpcc.so => not found
......
libc.so.6 => /usr/lib64/libc.so (0x00007f0377ade000)
The libccellprotein.so was lost.
next reply other threads:[~2022-04-06 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 7:03 蔺小渊 [this message]
2022-04-06 8:04 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A1261E8E-8819-4C0A-A594-54A68E5B62C2@163.com \
--to=shenxiaogll@163.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).