From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68676 invoked by alias); 27 Feb 2019 05:11:39 -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 68665 invoked by uid 89); 27 Feb 2019 05:11:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=whoever, asks, social, inflated X-HELO: gproxy6-pub.mail.unifiedlayer.com Received: from outbound-ss-348.hostmonster.com (HELO gproxy6-pub.mail.unifiedlayer.com) (74.220.202.212) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Feb 2019 05:11:37 +0000 Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 184D81E1E26 for ; Tue, 26 Feb 2019 22:07:18 -0700 (MST) Received: from box867.bluehost.com ([69.195.124.67]) by cmsmtp with ESMTP id yrR7gIeermds9yrR7g4FZj; Tue, 26 Feb 2019 22:07:18 -0700 Received: from 99-106-192-34.lightspeed.ftwotx.sbcglobal.net ([99.106.192.34]:58106 helo=[192.168.1.64]) by box867.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gyrR7-0047Y5-Ok for cygwin@cygwin.com; Tue, 26 Feb 2019 22:07:17 -0700 From: Vince Rice Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64 Date: Wed, 27 Feb 2019 05:57:00 -0000 References: <302c5d5e-be0d-74f9-9f9e-4b359683d092@yahoo.com> <5c75f963.1c69fb81.3637a.6314@mx.google.com> To: cygwin@cygwin.com In-Reply-To: Message-Id: X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00471.txt.bz2 > On Feb 26, 2019, at 8:55 PM, Jerry Baker wrote: >=20 > I don't work for free, This is open source. Given that the people here do, that's not a very good = argument. > especially for hostile people with over inflated egos and crippling socia= l disorders. Don't feed it by arguing. > The onus is on whoever is interested in having cygwin work in this partic= ular configuration. Again, this is open source; there is no onus. Win7x64 is a very common cygwin installation (including one of my VM's, whi= ch has no issues with 3.x). You're the only one reporting the problem. If this wer= e a general Win7x64 problem, the list would have exploded by now. You're the only who h= as access to your system. Consequently, you're the only one that's going to be= able to debug it. There's nothing obvious (to me, anyway) in your cygcheck.out. If = you don't care enough to debug it, that's not a problem; just live with 2.x for as lo= ng as 2.x will continue to work. You might try strace'ing a cygwin program and see if anything obvious shows= up in the output. Look for Windows errors, permission errors, etc. (Don't send it= here unless someone asks for it). See the User's Guide (https://cygwin.com/cygwin-ug-ne= t.html) for info on strace. -- 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