From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99885 invoked by alias); 19 Mar 2018 21:31:38 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 99875 invoked by uid 89); 19 Mar 2018 21:31:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-24.5 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=died, State X-HELO: relay1.mentorg.com Date: Mon, 19 Mar 2018 21:31:00 -0000 From: Joseph Myers To: Samuel Thibault CC: , Agustina Arzille Subject: Re: [hurd,commited] hurd: Reimplement libc locks using mach's gsync In-Reply-To: Message-ID: References: <20180318172408.19540-1-samuel.thibault@ens-lyon.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2018-03/txt/msg00480.txt.bz2 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