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=u4Za+GWtQ8JPhghxmHY7kjVhuULNw/1SDJ5O+eK3ddV2OuO23NUtR
	h5jbTg+2QzYWZ591y2y07cyUFCqc6E1t9c7SX2td20uaVLSkOa1rwSdjUvIIQqZR
	ssBIen5HL/jMUFrqGLRzVUHz4twXIbYA8Gy1n/kb3C5A3BQu6fFsX0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 26 Aug 2013 09:51:35 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
Message-ID: <20130826135135.GA4161@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> <CA+sc5mnedD0hOfzwTWYzy0QVhKC9gg-C68Nxfska-HG0HFOpLQ@mail.gmail.com> <20130823094919.GT2562@calimero.vinschen.de> <52178ED2.4090806@etr-usa.com> <5217A8A2.7060700@cygwin.com> <20130823191601.GA1446@ednor.casa.cgf.cx> <CA+sc5mk4UEqfZKvLtuwdrh0F_WwHd81FxtaN4+1L=7uVgMO=BQ@mail.gmail.com> <20130825172618.GB331@ednor.casa.cgf.cx> <20130826090406.GC18959@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130826090406.GC18959@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Mon, Aug 26, 2013 at 11:04:06AM +0200, Corinna Vinschen wrote:
>On Aug 25 13:26, Christopher Faylor wrote:
>> 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.
>
>We shouldn't overburden the CYGWIN env var with lots of tiny, nagging
>settings which are just as easy to keep in all the time.  Letting the
>32 bit version of Cygwin run 64 bit apps...
>
>> >And what about the other direction?
>> 
>> Apparently "vice versa" is not a universally understood term.
>
>...and vice versa doesn't cost us anything.  We add a FAQ people can be
>pointed to and that's it.

When I said "vice versa", I meant that we might need the same clear
warning for 64-bit programs running on 32-bit platforms.  I'm still not
clear on why this requires so much clarification.  But that's all right.
No need to enlighten me.  I'll just chalk this up to the Cygwin mailing
list confusion vortex.

You know I'm not a big fan of adding options to the CYGWIN environment
variable but I'm less of a fan of having people whine about something
not working, indignantly telling them to read the FAQ, and then having
them whine that there is no workaround.

This could all be a non-issue.  I was just trying to brainstorm and
think ahead.  But there's always that pesky vortex.

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