From: Joseph Myers <joseph@codesourcery.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: <libc-alpha@sourceware.org>, Agustina Arzille <avarzille@riseup.net>
Subject: Re: [hurd,commited] hurd: Reimplement libc locks using mach's gsync
Date: Mon, 19 Mar 2018 21:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1803192130410.19523@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1803191644190.4537@digraph.polyomino.org.uk>
On Mon, 19 Mar 2018, Joseph Myers wrote:
> > diff --git a/manual/errno.texi b/manual/errno.texi
> > index 73272fd884..8917cccb1e 100644
> > --- a/manual/errno.texi
> > +++ b/manual/errno.texi
> > @@ -882,6 +882,16 @@ the normal result is for the operations affected to complete with this
> > error; @pxref{Cancel AIO Operations}.
> > @end deftypevr
> >
> > +@deftypevr Macro int EOWNERDEAD
> > +@standards{GNU, errno.h}
> > +@errno{EOWNERDEAD, 120, Owner died}
> > +@end deftypevr
> > +
> > +@deftypevr Macro int ENOTRECOVERABLE
> > +@standards{GNU, errno.h}
> > +@errno{ENOTRECOVERABLE, 121, State not recoverable}
> > +@end deftypevr
>
> In general I'd expect changes to errno.texi to be accompanied by
> regeneration of sysdeps/gnu/errlist.c. Does such a regeneration result in
> no changes to the file, not even to the position in which these errno
> codes appear therein?
In fact, I'm seeing duplicate entries in sysdeps/gnu/errlist.c created
after this change. Maybe these errors need removing from the
Linux-specific section as well?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-03-19 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 17:24 Samuel Thibault
2018-03-19 16:57 ` Joseph Myers
2018-03-19 21:31 ` Joseph Myers [this message]
2018-03-20 1:59 ` Samuel Thibault
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=alpine.DEB.2.20.1803192130410.19523@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=avarzille@riseup.net \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@ens-lyon.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).