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] hurd: Add strlcpy, strlcat, wcslcpy, wcslcat to libc.abilist Date: Thu, 15 Jun 2023 08:15:31 +0000 (GMT) [thread overview] Message-ID: <20230615081531.08EC63854179@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=388ae538ddcb05c7d8966147b488a5f6e481656e commit 388ae538ddcb05c7d8966147b488a5f6e481656e Author: Florian Weimer <fweimer@redhat.com> Date: Thu Jun 15 10:05:25 2023 +0200 hurd: Add strlcpy, strlcat, wcslcpy, wcslcat to libc.abilist Diff: --- sysdeps/mach/hurd/x86_64/libc.abilist | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/sysdeps/mach/hurd/x86_64/libc.abilist b/sysdeps/mach/hurd/x86_64/libc.abilist index a0be5c1a87..24db98d765 100644 --- a/sysdeps/mach/hurd/x86_64/libc.abilist +++ b/sysdeps/mach/hurd/x86_64/libc.abilist @@ -447,6 +447,8 @@ GLIBC_2.38 __strdup F GLIBC_2.38 __strerror_r F GLIBC_2.38 __strfmon_l F GLIBC_2.38 __strftime_l F +GLIBC_2.38 __strlcat_chk F +GLIBC_2.38 __strlcpy_chk F GLIBC_2.38 __strncasecmp_l F GLIBC_2.38 __strncat_chk F GLIBC_2.38 __strncpy_chk F @@ -514,6 +516,8 @@ GLIBC_2.38 __wcscat_chk F GLIBC_2.38 __wcscoll_l F GLIBC_2.38 __wcscpy_chk F GLIBC_2.38 __wcsftime_l F +GLIBC_2.38 __wcslcat_chk F +GLIBC_2.38 __wcslcpy_chk F GLIBC_2.38 __wcsncasecmp_l F GLIBC_2.38 __wcsncat_chk F GLIBC_2.38 __wcsncpy_chk F @@ -1843,6 +1847,8 @@ GLIBC_2.38 strfroml F GLIBC_2.38 strfry F GLIBC_2.38 strftime F GLIBC_2.38 strftime_l F +GLIBC_2.38 strlcat F +GLIBC_2.38 strlcpy F GLIBC_2.38 strlen F GLIBC_2.38 strncasecmp F GLIBC_2.38 strncasecmp_l F @@ -2040,6 +2046,8 @@ GLIBC_2.38 wcscspn F GLIBC_2.38 wcsdup F GLIBC_2.38 wcsftime F GLIBC_2.38 wcsftime_l F +GLIBC_2.38 wcslcat F +GLIBC_2.38 wcslcpy F GLIBC_2.38 wcslen F GLIBC_2.38 wcsncasecmp F GLIBC_2.38 wcsncasecmp_l F
reply other threads:[~2023-06-15 8:15 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=20230615081531.08EC63854179@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).