From: Florian Weimer <fw@deneb.enyo.de>
To: "Y.D. via Libc-help" <libc-help@sourceware.org>
Subject: Re: Add a new function to dlfcn.h?
Date: Sun, 16 Aug 2020 14:59:03 +0200 [thread overview]
Message-ID: <87y2meiw6g.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAF6YOcM5NJmrjDvcaps7d6g8QkbBzL0jPK3Nsb6TeTu0LP8FdQ@mail.gmail.com> (Y. D. via Libc-help's message of "Sun, 16 Aug 2020 20:52:00 +0800")
* Y. D. via Libc-help:
> The question is, when I want to imitate the way dlopen works, I find that
> the dlopen first calls functions in dlfcn/dlopen.c, and then functions in
> elf/dl-open.c, which makes me very confused.
> If I want to add a new function in dlfcn.h, what should I do?
New dynamic linker functions should probably go into libc.so.6, and
implemented under elf/.
There is not much value in maintaining a separate libdl (but it's less
problematic than libpthread). I expect that libdl will eventually go
away.
next prev parent reply other threads:[~2020-08-16 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 12:52 Y.D.
2020-08-16 12:59 ` Florian Weimer [this message]
2020-08-17 2:15 ` Y.D.
2020-08-25 12:46 ` Florian Weimer
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=87y2meiw6g.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@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).