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=w4FekqKE94jCRTMmx3vZllQQoDtPqdkNA1LG2UuvCDvawJMU9JPmd
	YTC1queiuK29v1GGlQ+7wl13u4uKQeNLWdxHzf/UOfilhUnSU7yTiKXIfjE4NE+O
	zKlzWyXG10BEjQPEIZqxrxqXa0F7YX2stJfUy79woJt+h1H1dy8yw4=
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 11:04:06 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
Message-ID: <20130826090406.GC18959@calimero.vinschen.de>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="xo44VMWPx7vlQ2+2"
Content-Disposition: inline
In-Reply-To: <20130825172618.GB331@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.21 (2010-09-15)

--xo44VMWPx7vlQ2+2
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> >What about CYGWIN=3D32bitCygwinExec or some such?
>=20
> 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?
>=20
> 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.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--xo44VMWPx7vlQ2+2
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJSGxoFAAoJEPU2Bp2uRE+gy88P/1wZJvdXLAZsN+uo1eA7HoYe
8AAk/otroMFnwyGCk+CvyY+TBOrVOuysyfdvvIYM4Z9jrhWkret0mLvbf7oN5eGn
JJtbbOl36Qn+kw3+Hy69qZ+GNhb0FYJ9Fik4vzDR1abIKf07y9L+UHjnHQZqGsEJ
t4GTQ/+q+mNuXMAsjR/H8DqpGVfGbBjAc+ujCeuH1gZu1kRuZggp3dZBdoOQ22se
RH/UPV2cwBmFSWKf7OnZeJiCpt6EnXrqnezdIvj2Z2yfGahlv9MLL0QSTpoBxxkE
0OEijHvfN/sgpXjTqce8SvxYEmz8RtDJNZ3KYimWwQCJpsfDY5zyvA8pLQChjFVq
qm/dl0gyKJJnJ+UYyTDuF8YrRl0L8dOEHDoVjRjXOXLcebv5/GlOFDe0ONMW7TNM
qAHYDK1IfVe+XUJfEkfjbvFBG4TBWQ/FKXpX2Jocn3Gq347fDbjtZfZDuyN8lTgn
CTYOXfdQMAAbW2IOaPUsgur1mCPwyTWKqEm0IX69CLmC0ORZEohEQQC1hralGYq/
CWwnYTXs1ndQFq1h2ADDKMEcRcSkoa9bwYmRQAol/DpRZfXeVxX0wM/PAixSj2pV
oXgu6yjyUQu/1aDAhc5ShQxSl1P0/OgOgO9NyXXM9v3TotEZKZYDicGO+DT7jMKg
N+VQ/X4YaThTnYWg5CR5
=9oM9
-----END PGP SIGNATURE-----

--xo44VMWPx7vlQ2+2--