From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66149 invoked by alias); 26 Feb 2019 18:44:37 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 66114 invoked by uid 89); 26 Feb 2019 18:44:36 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=investigate X-HELO: mail-lj1-f172.google.com Received: from mail-lj1-f172.google.com (HELO mail-lj1-f172.google.com) (209.85.208.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 26 Feb 2019 18:44:35 +0000 Received: by mail-lj1-f172.google.com with SMTP id v10so11730314lji.3 for ; Tue, 26 Feb 2019 10:44:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=nclqTFJIKOZNaEHlzAl3SFSvcwRPE7lBLysiTL81buE=; b=Y59wJ0FTwjyWoeEwoWsPKRlK/dmM1S9mVMg5bUIPqvuNusCCkvTR1YKCwj9bifqaVk GA7Kr4pzhbfQZ/SrQtxEg1KmbIdSolQBfEoSIFF7iGouWflJsngESTGXXMMDxEq2vmne hmdhVC/WpeZYvvONQP2mGUIP91/WsjME5IHdnN86CWYk8OAYUdJIrSaav1OrWzXLkoku mUeA/lenlZcZpnb3T+k3XaizMJlLu67FXpR368hoMnxsceyRd29W7yq7+VX07Dmrl/sU NqG1UKfJ3KYwo0qssGcTHJRT8TyqH9nSDG2etsqEVF/mUij3o/piexCeUh9Tt/YWAv0G g3JQ== MIME-Version: 1.0 References: <9e344bdc-758b-5711-b25a-1ed2e46952be@yahoo.com> <746a01c6-0faf-aff3-51e6-c0e129a56cc4@yahoo.com> <110b2dfb62fa274469d2d2fae586fb99@smtp-cloud7.xs4all.net> In-Reply-To: From: Richard Campbell Date: Tue, 26 Feb 2019 18:45:00 -0000 Message-ID: Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64 To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00446.txt.bz2 On Tue, Feb 26, 2019 at 12:38 PM Jerry Baker via cygwin wrote: > > That's why you're reading about it "on the appropriate list," as > described on that page. It's a take it or leave it thing. I report it, > and the cygwin community can do whatever they like with it - ignore it, > investigate it, shoot the messenger. It's their project. The requested cygcheck output would be helpful in this regard. "Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed." -Richard Campbell. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple