public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Remove spurious references to _dl_open_hook Date: Mon, 1 Aug 2022 13:50:47 +0000 (GMT) [thread overview] Message-ID: <20220801135047.1BC943858D39@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=032712621fd376def8ee4c1d997b414f29a30108 commit 032712621fd376def8ee4c1d997b414f29a30108 Author: Florian Weimer <fweimer@redhat.com> Date: Mon Aug 1 15:49:07 2022 +0200 Remove spurious references to _dl_open_hook _dl_open_hook was removed in commit 466c1ea15f461edb8e3ffaf5d86d708 ("dlfcn: Rework static dlopen hooks"). Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Diff: --- libio/vtables.c | 4 ---- malloc/arena.c | 5 ----- 2 files changed, 9 deletions(-) diff --git a/libio/vtables.c b/libio/vtables.c index 499f0039cb..50acab7f21 100644 --- a/libio/vtables.c +++ b/libio/vtables.c @@ -25,10 +25,6 @@ void (*IO_accept_foreign_vtables) (void) attribute_hidden; -/* Used to detected multiple libcs. */ -extern struct dl_open_hook *_dl_open_hook; -libc_hidden_proto (_dl_open_hook); - #else /* !SHARED */ /* Used to check whether static dlopen support is needed. */ diff --git a/malloc/arena.c b/malloc/arena.c index 0a684a720d..defd25c8a6 100644 --- a/malloc/arena.c +++ b/malloc/arena.c @@ -300,11 +300,6 @@ next_env_entry (char ***position) #endif -#ifdef SHARED -extern struct dl_open_hook *_dl_open_hook; -libc_hidden_proto (_dl_open_hook); -#endif - #if USE_TCACHE static void tcache_key_initialize (void); #endif
reply other threads:[~2022-08-01 13:50 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220801135047.1BC943858D39@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).