From: Kamil Rytarowski <n54@gmx.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
Matthew Bauer <mjbauer95@gmail.com>,
libstdc++@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdcxx: Update ctype_base.h from NetBSD upstream
Date: Sun, 22 Dec 2019 14:06:00 -0000 [thread overview]
Message-ID: <3ef9d04d-a508-7f53-b4d2-a68c9d7859eb@gmx.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1912161021450.3227@anthias>
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
On 22.12.2019 00:36, Gerald Pfeifer wrote:
> Hi Matthew,
>
> On Mon, 4 Feb 2019, Matthew Bauer wrote:
>> The ctype_base.h file in libstdc++-v3 is out of date for NetBSD. They
>> have changed their ctype.h definition. It was updated in their intree
>> libstdc++-v3 but not in the GCC one. My understanding is this is a
>> straightforward rewrite. I've attached my own patch, but the file can
>> be obtained directly here:
>>
>> http://cvsweb.netbsd.org/bsdweb.cgi/src/external/gpl3/gcc/dist/libstdc%2b%2b-v3/config/os/bsd/netbsd/ctype_base.h
>>
>> With the attached patch, libstdc++-v3 can succesfully be built with
>> NetBSD headers (along with --disable-libcilkrts).
>
> I noticed this has not been applied yet, nor seen a follow-up?, and also
> noticed it went to the gcc-patches list, but not libstdc++@gcc.gnu.org.
>
> Let me re-address this to libstdc++@gcc.gnu.org in the hope the
> maintainers there will have a look.
>
> Gerald
>
We (in NetBSD) wait for this to be merged.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-22 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFnZKr1EPETS4CNu0rHwkhWSGRDt_e0TJpjUPTfSeDywDXyVRg@mail.gmail.com>
2019-12-21 23:37 ` Gerald Pfeifer
2019-12-22 14:06 ` Kamil Rytarowski [this message]
2019-12-23 10:33 ` Jonathan Wakely
2020-01-06 15:24 ` Jonathan Wakely
2020-01-06 22:20 ` Kamil Rytarowski
2020-01-07 0:26 ` Jonathan Wakely
2020-01-07 0:31 ` Kamil Rytarowski
2020-01-07 15:40 ` Jonathan Wakely
2020-01-07 15:43 ` Jonathan Wakely
2020-01-07 20:44 ` Jason Thorpe
2020-01-10 17:54 ` Jonathan Wakely
2020-01-14 16:56 ` Kamil Rytarowski
2020-01-14 21:25 ` Jason Thorpe
2020-01-16 17:47 ` Jonathan Wakely
2020-01-16 21:38 ` Jason Thorpe
2020-01-06 15:34 ` Jonathan Wakely
2020-01-06 23:19 ` Kamil Rytarowski
2020-01-07 0:28 ` Jonathan Wakely
2020-01-07 0:54 ` Kamil Rytarowski
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=3ef9d04d-a508-7f53-b4d2-a68c9d7859eb@gmx.com \
--to=n54@gmx.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mjbauer95@gmail.com \
/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).