From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: FW: [PATCH] [RFC] newlib: libc: start manual appendix to hold various ABI constants
Date: Tue, 23 Jan 2024 23:37:03 -0500 [thread overview]
Message-ID: <ZbCT7yWjp3SpdRGV@vapier> (raw)
In-Reply-To: <98c7546a-2caf-4492-b5e8-882f5d867262@systematicsw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On 23 Jan 2024 14:05, brian.inglis@systematicsw.ab.ca wrote:
> On 2023-12-29 22:03, Mike Frysinger wrote:
> > On 29 Dec 2023 20:17, C Howland wrote:
> >> I won't comment on whether adding this is a good idea or not as I
> >> don't meet any of the stated use cases. But here are a few thoughts on the
> >> details of it assuming others like the addition.
> >
> > if you only use newlib, it could be helpful. consider how common it is for
> > people to write error messages like:
> > printf("error %i\n", errno);
> > so your log contains "error 13". how do you find out what errno 13 is ?
> > even Linux's `man errno` doesn't list the raw numbers. having online access
> > to the name<->number mappings for these is helpful in a pinch in my experience.
>
> moreutils errno?
>
> https://joeyh.name/code/moreutils/
> https://repology.org/project/moreutils/versions
>
> - perhaps with creative use of "locales" (or patches) for different library
> sources and board support?
right, it currently only works for the current ABI. and requires you be
running a *NIX compatible system. i think it's not uncommon for people to
have Windows as their main desktop in the embedded space. i know Windows
has been gaining Linux layers, but still seems over the top to look up a
number/constant.
might also be worth seeing if they're interested in expanding as you suggest,
but it's not something i'm going to look into tbh.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-24 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 7:25 Mike Frysinger
[not found] ` <BN2P110MB15445C61D8D69733C10DA4D99A9CA@BN2P110MB1544.NAMP110.PROD.OUTLOOK.COM>
2023-12-30 1:17 ` FW: " C Howland
2023-12-30 5:03 ` Mike Frysinger
2024-01-23 21:05 ` brian.inglis
2024-01-24 4:37 ` Mike Frysinger [this message]
2024-01-23 9:15 ` Corinna Vinschen
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=ZbCT7yWjp3SpdRGV@vapier \
--to=vapier@gentoo.org \
--cc=newlib@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).