From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <HBBroeker@t-online.de>
Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83])
 by sourceware.org (Postfix) with ESMTPS id DE9F93858D20
 for <cygwin@cygwin.com>; Thu, 17 Feb 2022 23:11:42 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DE9F93858D20
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=t-online.de
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=t-online.de
Received: from fwd71.dcpf.telekom.de (fwd71.aul.t-online.de [10.223.144.97])
 by mailout07.t-online.de (Postfix) with SMTP id B503EB686
 for <cygwin@cygwin.com>; Fri, 18 Feb 2022 00:11:41 +0100 (CET)
Received: from [192.168.178.26] ([79.228.92.68]) by fwd71.t-online.de
 with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted)
 esmtp id 1nKpw4-3jIKWG0; Fri, 18 Feb 2022 00:11:40 +0100
Message-ID: <1032c1c3-21a7-3e37-96f5-2158080efa7d@t-online.de>
Date: Fri, 18 Feb 2022 00:11:36 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Subject: Re: [:xdigit:] does not work with std::wstring in a Cygwin environment
Content-Language: de-DE
To: cygwin@cygwin.com
References: <53a83ef8dcc847e2914be35aa8c4525a@brillux.de>
 <87tud2mxn1.fsf@Rainer.invalid>
 <03ac7dd2-7082-2bb1-6c1b-c230764216e2@t-online.de>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker@t-online.de>
In-Reply-To: <03ac7dd2-7082-2bb1-6c1b-c230764216e2@t-online.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-TOI-EXPURGATEID: 150726::1645139500-00001674-08051FF6/0/0 CLEAN NORMAL
X-TOI-MSGID: 3af6ec62-a7f3-4d93-b72c-b60f0fd8d4e7
X-Spam-Status: No, score=2.5 required=5.0 tests=BAYES_00, FREEMAIL_FROM,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A,
 RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,
 SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2022 23:11:44 -0000

Am 15.02.2022 um 02:36 schrieb Hans-Bernhard Bröker:
> Am 13.02.2022 um 19:25 schrieb Achim Gratz:

>> There is no OS specific configuration for Cygwin explicitly, instead
>> there is one for newlib that actually gets used.

> This piqued my curiosity, so I had a look at how libstdc++ is built.  I
> found that at least for one crucial source file, called
> ctype_members.cc, cygwin builds do _not_ use the newlib edition, but
> rather the "generic" one.  And that may very well be the problem here.
[...]

I've taken the liberty of filing this upstream as a GCC/libstdc++ issue.

The extremely condensed version of the issue is that libstdc++ builds by 
selecting config/os/newlib, but it does not pick --enable-clocale=newlib.

Enabling the more global --with-newlib flag would do the latter for us, 
but it might have other, less desirable effects on top of that.