delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:from:content-type:content-transfer-encoding | |
:mime-version:subject:date:references:to:in-reply-to:message-id; | |
q=dns; s=default; b=ZTVazRAKtBjEDQapeTu03CEnREPEwwBEqnWSSpIzlLe | |
M0QQZpINNz3rNfeR380ojWXw640DWq8iaUhE9IefzsUdym91qUd0LcnRkl4ZiBwI | |
ZKsvhDdZ2DQ2uqL7K/n//tocmpIdndgzwHCp6fg2KtfnCrKWFZ3PlUkQLzesypxw | |
= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:from:content-type:content-transfer-encoding | |
:mime-version:subject:date:references:to:in-reply-to:message-id; | |
s=default; bh=Jj6dQiiI9q5zMZRsyZ5/lAvvbtU=; b=yVs/t6Yo9P/GFlS7j | |
d5+M0N1m3DAYlU6Ra6nqDAdsEZHHLdvRci1jUkZCpYVL+zqncBwKaiQNTy3erf6C | |
gWCLnVAQTKpZK+pqVTBTorjy2tb+RPi1Ud/0w+RbHU433xGCNERVzz5wqBTUQ+ci | |
PDVLpV+FQc5doeTksW+1S2YIKw= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
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 |
From: | Vince Rice <vrice AT solidrocksystems DOT com> |
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: | Tue, 26 Feb 2019 23:07:15 -0600 |
References: | <302c5d5e-be0d-74f9-9f9e-4b359683d092 AT yahoo DOT com> <5c75f963 DOT 1c69fb81 DOT 3637a DOT 6314 AT mx DOT google DOT com> <ff1c278a-d9e8-eea2-e770-5e07d2417c77 AT yahoo DOT com> |
To: | cygwin AT cygwin DOT com |
In-Reply-To: | <ff1c278a-d9e8-eea2-e770-5e07d2417c77@yahoo.com> |
Message-Id: | <FE953DCF-FB42-46D6-8B8D-50009CC07F97@solidrocksystems.com> |
X-IsSubscribed: | yes |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id x1R5Bm4n027331 |
> On Feb 26, 2019, at 8:55 PM, Jerry Baker wrote: > > 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 social disorders. Don't feed it by arguing. > The onus is on whoever is interested in having cygwin work in this particular configuration. Again, this is open source; there is no onus. Win7x64 is a very common cygwin installation (including one of my VM's, which has no issues with 3.x). You're the only one reporting the problem. If this were a general Win7x64 problem, the list would have exploded by now. You're the only who has 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 long 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-net.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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |