This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [hurd,commited] hurd: Reimplement libc locks using mach's gsync


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]