From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: libc-alpha@sourceware.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>, commit-hurd@gnu.org
Subject: [hurd,commited] hurd: Export _hurd_libc_proc_init
Date: Mon, 12 Apr 2021 00:23:56 +0200 [thread overview]
Message-ID: <20210411222356.3239825-1-samuel.thibault@ens-lyon.org> (raw)
hurd's libdiskfs needs to be able to call _hurd_init + _hurd_libc_proc_init
for bootstrap initialization.
---
hurd/Versions | 5 +++++
hurd/hurd.h | 3 +++
sysdeps/mach/hurd/i386/libc.abilist | 1 +
3 files changed, 9 insertions(+)
diff --git a/hurd/Versions b/hurd/Versions
index b66d37be07..7e4f1c5630 100644
--- a/hurd/Versions
+++ b/hurd/Versions
@@ -138,6 +138,11 @@ libc {
_hurd_port_move;
}
+ GLIBC_2.34 {
+ # "quasi-internal" functions
+ _hurd_libc_proc_init;
+ }
+
HURD_CTHREADS_0.3 {
# weak refs to libthreads functions that libc calls iff libthreads in use
__cthread_fork; __pthread_create; __cthread_detach; __pthread_detach;
diff --git a/hurd/hurd.h b/hurd/hurd.h
index 986080c819..51c3f9c1a1 100644
--- a/hurd/hurd.h
+++ b/hurd/hurd.h
@@ -275,6 +275,9 @@ extern void _hurd_init (int flags, char **argv,
mach_port_t *portarray, size_t portarraysize,
int *intarray, size_t intarraysize);
+/* Register the process to the proc server. */
+extern void _hurd_libc_proc_init (char **argv);
+
/* Do startup handshaking with the proc server, and initialize library data
structures that require proc server interaction. This includes
initializing signals; see _hurdsig_init in <hurd/signal.h>. */
diff --git a/sysdeps/mach/hurd/i386/libc.abilist b/sysdeps/mach/hurd/i386/libc.abilist
index 7424dc9166..fcba25ee5e 100644
--- a/sysdeps/mach/hurd/i386/libc.abilist
+++ b/sysdeps/mach/hurd/i386/libc.abilist
@@ -2206,6 +2206,7 @@ GLIBC_2.33 stat F
GLIBC_2.33 stat64 F
GLIBC_2.34 __isnanf128 F
GLIBC_2.34 __libc_start_main F
+GLIBC_2.34 _hurd_libc_proc_init F
GLIBC_2.4 __confstr_chk F
GLIBC_2.4 __fgets_chk F
GLIBC_2.4 __fgets_unlocked_chk F
--
2.30.2
reply other threads:[~2021-04-11 22:24 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=20210411222356.3239825-1-samuel.thibault@ens-lyon.org \
--to=samuel.thibault@ens-lyon.org \
--cc=commit-hurd@gnu.org \
--cc=libc-alpha@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).