From: Florian Weimer <fweimer@redhat.com>
To: PODOPLELOV Andrei <Andrei.PODOPLELOV@3ds.com>
Cc: "mtk.manpages@gmail.com" <mtk.manpages@gmail.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"alx.manpages@gmail.com" <alx.manpages@gmail.com>
Subject: Re: [patch] --filter option in ld: srcfix
Date: Wed, 08 Dec 2021 21:07:45 +0100 [thread overview]
Message-ID: <87pmq6j1wu.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <64a06ee4b44648ccad3dfee1f3d1af1a@3ds.com> (PODOPLELOV Andrei's message of "Wed, 8 Dec 2021 17:32:36 +0000")
* PODOPLELOV Andrei:
> I believe it would be beneficial to change it to something like:
>
> --filter=name
> When creating an ELF shared object (a "filter"), set the
> internal DT_FILTER field to the specified name - another
> ELF shared object (a "filtee"). This tells the dynamic linker
> that the symbol table of the "filter" should be used to
> select a subset of the symbols provided by the "filtee".
>
> When you link a program against this "filter" and run it,
> the dynamic linker will see the DT_FILTER field and resolve
> symbols according to the symbol table of the "filter" object
> as usual. However, when a certain symbol of the "filter" is
> also present in "filtee", it will actually link to the
> definition in the "filtee".
I think that's still misleading because to my knowledge, glibc does not
implement any filtering. Only the symbol search order is changed (what
you describe in the second paragraph).
Thanks,
Florian
next prev parent reply other threads:[~2021-12-08 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:32 [patch] --filter option in ld: srcfix PODOPLELOV Andrei
2021-12-08 20:07 ` Florian Weimer [this message]
2021-12-09 1:08 ` PODOPLELOV Andrei
2021-12-09 15:35 ` Florian Weimer
2021-12-09 16:32 ` PODOPLELOV Andrei
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=87pmq6j1wu.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=Andrei.PODOPLELOV@3ds.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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