public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH,hurd] Fix arbitrary error code
Date: Tue, 12 Apr 2022 11:57:42 +0200	[thread overview]
Message-ID: <20220412095742.ebmvavh2rhr63kcj@begin> (raw)
In-Reply-To: <87h76yhblu.fsf@oldenburg.str.redhat.com>

Florian Weimer, le mar. 12 avril 2022 11:53:01 +0200, a ecrit:
> > +++ b/nss/nss_test_errno.c
> > @@ -28,7 +28,13 @@ static void __attribute__ ((constructor))
> >  init (void)
> >  {
> >    /* An arbitrary error code which is otherwise not used.  */
> > +#if defined(__linux__)
> >    errno = ELIBBAD;
> > +#elif defined(__GNU__)
> > +  errno = EGRATUITOUS;
> > +#else
> > +#error missing arbitrary error code
> > +#endif
> >  }
> >  
> >  /* Lookup functions for pwd follow that do not return any data.  */
> 
> I don't see a build failure because of this?

The build failure happens during make check, not during make.

> Maybe we can pick another shared error code?

Yep, sure, I'm just not sure what should be used.

> Related question: Would it be possible to add ELIBEXEC to Hurd some day?

That should be easy to implement, yes. We can already just enable its
definition in glibc, and we'll be able to implement it in Hurd's exec
server.

Samuel

  reply	other threads:[~2022-04-12  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  9:44 Samuel Thibault
2022-04-12  9:53 ` Florian Weimer
2022-04-12  9:57   ` Samuel Thibault [this message]
2022-04-12 10:31     ` Florian Weimer
2022-04-12 20:18       ` Samuel Thibault
2022-04-12 20:45     ` 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=20220412095742.ebmvavh2rhr63kcj@begin \
    --to=samuel.thibault@ens-lyon.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).