From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from endymion.arp.harvard.edu (endymion.arp.harvard.edu [140.247.179.94]) by sourceware.org (Postfix) with ESMTPS id 2030B3851C0E for ; Wed, 18 Nov 2020 00:24:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2030B3851C0E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=huarp.harvard.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=allen@huarp.harvard.edu Received: from [192.168.7.23] (pool-74-104-152-231.bstnma.fios.verizon.net [74.104.152.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by endymion.arp.harvard.edu (Postfix) with ESMTPSA id 638636C094B for ; Tue, 17 Nov 2020 19:24:13 -0500 (EST) Subject: Re: cmake suddenly stopped working From: Norton Allen To: "cygwin@cygwin.com" References: <2f4aa73e-781e-ba06-f230-4fa884715988@maxrnd.com> <3ccdc37d-953f-f6a5-76af-56e201ee864a@huarp.harvard.edu> <0c91c91e-70e5-093a-0b61-07b76a52fc4a@huarp.harvard.edu> Message-ID: Date: Tue, 17 Nov 2020 19:24:12 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <0c91c91e-70e5-093a-0b61-07b76a52fc4a@huarp.harvard.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2020 00:24:33 -0000 Rolling back cmake from 3.17.3-2 to 3.14.5-1 seems to have resolved the problem. Any idea why no one else seems to be seeing this problem with 3.17.3-2?