public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] hurd: Define ELIBEXEC
Date: Tue, 12 Apr 2022 20:17:42 +0000 (GMT)	[thread overview]
Message-ID: <20220412201742.E18C23857C4A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=45a8e05785a617683bbaf83f756cada7a4a425b9

commit 45a8e05785a617683bbaf83f756cada7a4a425b9
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Tue Apr 12 22:16:38 2022 +0200

    hurd: Define ELIBEXEC
    
    So we can implement it in the exec server.

Diff:
---
 manual/errno.texi              | 10 +++++-----
 sysdeps/mach/hurd/bits/errno.h |  2 ++
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/manual/errno.texi b/manual/errno.texi
index 9879ab43e6..28dd871caa 100644
--- a/manual/errno.texi
+++ b/manual/errno.texi
@@ -749,6 +749,11 @@ particular function will always fail with @code{ENOSYS} unless you
 install a new version of the C library or the operating system.
 @end deftypevr
 
+@deftypevr Macro int ELIBEXEC
+@standards{GNU, errno.h}
+@errno{ELIBEXEC, 83, Cannot exec a shared library directly}
+@end deftypevr
+
 @deftypevr Macro int ENOTSUP
 @standards{POSIX.1, errno.h}
 @errno{ENOTSUP, 118, Not supported}
@@ -1059,11 +1064,6 @@ They are not yet documented.}
 @errno{ELIBMAX, ???/82, Attempting to link in too many shared libraries}
 @end deftypevr
 
-@deftypevr Macro int ELIBEXEC
-@standards{Linux???, errno.h}
-@errno{ELIBEXEC, ???/83, Cannot exec a shared library directly}
-@end deftypevr
-
 @deftypevr Macro int ESTRPIPE
 @standards{Linux???, errno.h}
 @errno{ESTRPIPE, ???/86, Streams pipe error}
diff --git a/sysdeps/mach/hurd/bits/errno.h b/sysdeps/mach/hurd/bits/errno.h
index 8f2fbfd80f..0d935e724a 100644
--- a/sysdeps/mach/hurd/bits/errno.h
+++ b/sysdeps/mach/hurd/bits/errno.h
@@ -115,6 +115,7 @@ enum __error_t_codes
   EAUTH                          = 0x40000050,	/* Authentication error */
   ENEEDAUTH                      = 0x40000051,	/* Need authenticator */
   ENOSYS                         = 0x4000004e,	/* Function not implemented */
+  ELIBEXEC                       = 0x40000053,	/* Cannot exec a shared library directly */
   ENOTSUP                        = 0x40000076,	/* Not supported */
   EILSEQ                         = 0x4000006a,	/* Invalid or incomplete multibyte or wide character */
   EBACKGROUND                    = 0x40000064,	/* Inappropriate operation for background process */
@@ -312,6 +313,7 @@ enum __error_t_codes
 #define EAUTH                          0x40000050
 #define ENEEDAUTH                      0x40000051
 #define ENOSYS                         0x4000004e
+#define ELIBEXEC                       0x40000053
 #define ENOTSUP                        0x40000076
 #define EILSEQ                         0x4000006a
 #define EBACKGROUND                    0x40000064


                 reply	other threads:[~2022-04-12 20:17 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=20220412201742.E18C23857C4A@sourceware.org \
    --to=sthibaul@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: 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).