* Fwd: Newlib bouncing undelivered to me
[not found] <20210728152637.151E032379D@fx405.security-mail.net>
@ 2021-07-28 16:44 ` Brian Inglis
2021-07-28 16:46 ` Frank Ch. Eigler
0 siblings, 1 reply; 2+ messages in thread
From: Brian Inglis @ 2021-07-28 16:44 UTC (permalink / raw)
To: Sourceware Email Support, Overseers mailing list
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Please remove nbrunie@kalray.eu from the newlib mailing list as I am
getting bounce messages for every post, as presumably are all other
posters.
-------- Forwarded Message --------
Subject: Undelivered Mail Returned to Sender
Date: Wed, 28 Jul 2021 17:26:37 +0200 (CEST)
From: Mail Delivery System <MAILER-DAEMON@mi01.dcs.int.inet>
To: Brian.Inglis@systematicsw.ab.ca
This is the mail system at host fx405.security-mail.net.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<nbrunie@kalray.eu>: host zimbra2.kalray.eu[195.135.97.26] said: 550 5.1.1
<nbrunie@kalray.eu>: Recipient address rejected: User unknown in
virtual
mailbox table (in reply to RCPT TO command)
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
[-- Attachment #2: Attached Message Part --]
[-- Type: message/delivery-status, Size: 465 bytes --]
[-- Attachment #3: ForwardedMessage.eml --]
[-- Type: message/rfc822, Size: 5188 bytes --]
From: Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH 1/1] libc: Added implementations and prototypes for
Date: Wed, 28 Jul 2021 09:25:59 -0600
Message-ID: <57f33efa-2450-ac5c-3ceb-be8beb183ca5@SystematicSw.ab.ca>
On 2021-07-28 03:11, Corinna Vinschen wrote:
> Hi Matt,
>
> thanks for this v2.
>
> On Jul 24 10:37, Matt Joyce wrote:
>> Added implementations for sig2str() and str2sig() in libc/signal in order
>> to improve POSIX compliance. Added function prototypes to sys/signal.h.
>> Added Makefile.am entries to build the new file.
>> ---
>> [...]
>> +#if __GNU_VISIBLE
>
> I think this needs discussion. The sig2str/str2sig API has not been
> provided yet by GLibC. Using __GNU_VISIBLE in this context looks wrong.
> What we need, in fact, is a __POSIX_VISIBLE guard, but here's the
> problem: As far as I can see, the Issue 8 draft does not yet define a
> version number.
>
> If anybody has better information or a good idea how to guard this new
> API in the meantime, I'm all ears.
Current values are:
__POSIX_VISIBLE 199009
__POSIX_VISIBLE 199209
__POSIX_VISIBLE 199309
__POSIX_VISIBLE 199506
__POSIX_VISIBLE 200112
__POSIX_VISIBLE 200809
__POSIX_VISIBLE 201402
and anticipated release date is 2022 from FAQ
https://www.opengroup.org/austin/faq.html
Q8. Where is the schedule for draft development?
so could use:
__POSIX_VISIBLE >= 202202 /* FIXME when POSIX Issue 8 released */
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
^ permalink raw reply [flat|nested] 2+ messages in thread