X-Recipient: archive-cygwin@delorie.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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=HKGZIEStaa/3XNYTO8K4n7lEXC8gAJYrR6i/F2IX6lTd6Wv9xryLC 4TqbDPC0YFcGTQRvufTfr6TtUvM3H/4dP0Fjm5oL4PEspMGD6txP+bbKu4Rdg2vH f2MotXpQ4ZLFu/SaV4swXHDSBbmdaRJThJ0r9BGtzQ/FCAwKf43QVQ= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=DYS1BKISTYMgDlfYXyar6++/9Hc=; b=BSQX3RlG8qTL7kU/L9C4Ps4jpVs5 hario9ldNUsP4QSSMHGBgNiL/LEL/+WwDM3jO7TIjFexoj4RLMtZdVmNcC7K1u+h QJo/I/u59jjCWNHTQWGlU27lzSLvuWrYvG0UYBSYeh0iSDmj8CmYUWmphfRBhfa8 QNRFxX0mAzTQ/no= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.2 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/bpBrIC/ADHm6tg/VE87kO Date: Sun, 25 Aug 2013 13:26:18 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Why are the 32- and 64-bit cygwin1.dlls incompatible? Message-ID: <20130825172618.GB331@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <52162CA9.9080002@etr-usa.com> <20130822171419.GQ2562@calimero.vinschen.de> <20130823094919.GT2562@calimero.vinschen.de> <52178ED2.4090806@etr-usa.com> <5217A8A2.7060700@cygwin.com> <20130823191601.GA1446@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) On Sun, Aug 25, 2013 at 11:05:06AM -0400, Earnie Boyd wrote: >On Fri, Aug 23, 2013 at 3:16 PM, Christopher Faylor wrote: >>I was having a private chat with Corinna about this. >> >>Her doubts above mirror mine. I wonder if this will add to the traffic >>from people who, e.g., expect their java apps to understand Cygwin >>ptys. Now we will have people who don't understand why their 32-bit >>screen doesn't work under 64-bit Cygwin mintty. >> >>The original error message was certainly not clear but maybe we need to >>have something like: >> >>"Can't run 32-bit Cygwin programs in a 64-bit Cygwin environment" >> >>and vice versa with a, as you say, (ugh) way to turn this on and off. >What about CYGWIN=32bitCygwinExec or some such? Yes, we were talking about a CYGWIN environment variable. It would probably be something like "arch_mismatch". However, you're jumping to implementation when it isn't even clear if this is something that we want to do. >And what about the other direction? Apparently "vice versa" is not a universally understood term. >It is clear that some operations cannot occur especially pty but that >is still true with execing any Windows program. I don't see this >being too big an extra burden on support. If people don't understand why their Windows programs don't understand Cygwin ptys I'm sure that they won't understand why their Cygwin programs don't understand Cygwin ptys. We just, in fact, already saw this confusion, mainly because the error was even more confusing than normal. cgf -- 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