From: Ulrich Drepper <drepper@redhat.com>
To: binutils@sourceware.cygnus.com
Subject: DT_FILTER problem
Date: Fri, 21 Jul 2000 00:07:00 -0000 [thread overview]
Message-ID: <m3d7k8q7ve.fsf@otr.mynet.cygnus.com> (raw)
When using the -F/--filter option of ld the appropriate DT_FILTER
entry is created, but there is also a DT_NEEDED entry for the same
object. This is wrong. The following is the output of readelf on one
of my test programs:
0x00000001 (NEEDED) Shared library: [/work/glibc-builds/200
00720/elf/filtmod2.so]
0x7fffffff (FILTER) Filter library: [/work/glibc-builds/200
00720/elf/filtmod2.so]
Since the filter object itself is never used (only at link time by ld)
it makes no sense to add a DT_NEEDED entry. It might even cause
problems if the ld.so adds the object twice (because of the two
references).
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
next reply other threads:[~2000-07-21 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 0:07 Ulrich Drepper [this message]
2000-07-21 0:15 ` DT_FILTER problem [IGNORE] Ulrich Drepper
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=m3d7k8q7ve.fsf@otr.mynet.cygnus.com \
--to=drepper@redhat.com \
--cc=binutils@sourceware.cygnus.com \
/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).