public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Lucas Augusto Valentim Dantas <lucasvalentim@outlook.com.br>,
	 "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: errnos.h usage
Date: Wed, 14 Feb 2024 10:53:52 +0300	[thread overview]
Message-ID: <42e51cf234525f651706d3f3157f7394d7d301b7.camel@yandex.ru> (raw)
In-Reply-To: <ROAP284MB2203AF5516D8A7FEB4F452558A4E2@ROAP284MB2203.BRAP284.PROD.OUTLOOK.COM>

On Wed, 2024-02-14 at 04:59 +0000, Lucas Augusto Valentim Dantas via
Libc-help wrote:
> Hello, I have been playing around with Doom's source code, the 90s
> one, and I have noticed that it has a header included named errnos.h
> that I have recently learned that it was actually present in glibc
> beginning from 2.0.0 (I think) until 2.0.7. Could anyone shed light
> on why it was added to glibc and later removed?
>
> https://sources.debian.org/src/glibc/2.0.7t-1/sysdeps/unix/sysv/linux/errnos.h/
> https://github.com/id-Software/DOOM/blob/master/linuxdoom-1.10/i_video.c#L49

Judging by the commit 5107cf1d7d27f17c6de68ec15a8e8d9dd5b471c1 description from 1997:

>            * sysdeps/mach/hurd/errnos.h: -> .../bits/errno.h
>            * sysdeps/standalone/arm/errnos.h: Likewise.
>            * sysdeps/stub/errnos.h: Likewise.
>            * sysdeps/unix/bsd/bsd4.4/errnos.h: Likewise.
>            * sysdeps/unix/sysv/linux/errnos.h: Likewise.

all platform-specific `errnos.h` were merged into a single file `errno.h`.

  reply	other threads:[~2024-02-14  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  4:59 Lucas Augusto Valentim Dantas
2024-02-14  7:53 ` Konstantin Kharlamov [this message]
2024-02-14  7:58 ` Basile Starynkevitch

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=42e51cf234525f651706d3f3157f7394d7d301b7.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=libc-help@sourceware.org \
    --cc=lucasvalentim@outlook.com.br \
    /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).