From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id F2D7E3858C74 for ; Thu, 13 Jul 2023 05:52:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F2D7E3858C74 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 36D5rh81049026 for ; Wed, 12 Jul 2023 22:53:43 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 50-1-247-226.fiber.dynamic.sonic.net(50.1.247.226), claiming to be "[192.168.4.100]" via SMTP by m0.truegem.net, id smtpdc8udI3; Wed Jul 12 22:53:39 2023 Subject: Re: iostream doesn't work (clang++) To: cygwin@cygwin.com References: <7e07e251-2ec6-b7a5-62da-8578eb638993@gmail.com> <47f9e50d-763b-e6a9-b2b0-8d3cc311a63b@maxrnd.com> <3c02f650-248e-9e03-94a8-d508c857474e@gmail.com> From: Mark Geisert Message-ID: Date: Wed, 12 Jul 2023 22:52:29 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <3c02f650-248e-9e03-94a8-d508c857474e@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi once again, ggl329 via Cygwin wrote: > On 2023/07/05 12:06, Mark Geisert via Cygwin wrote: >> My previous reply addressed the specific error reported by your testcase. >> But I am unable to make progress on the root cause because I can't reproduce >> your report. [... useful info elided from this quote ...] I was able to build a working clang/clang++ environment and then reproduce your report. A potential solution was discussed on the cygwin-patches mailing list. Just a quick note to say the root cause has been fixed; the next version of the Cygwin DLL (3.4.8) will include the fix. If you need the fix urgently you can find a replacement for your /usr/include/sys/cpuset.h at https://github.com/cygwin/cygwin/blob/main/winsup/cygwin/include/sys/cpuset.h I would suggest moving (with 'mv') your existing file out of the way but keeping it around in case of any mishap getting the replacement. Thanks again for reporting this issue, ..mark