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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=GoI+Phy6D9QquFmYCLZTJG6csPYmb16GhwTq550jTzP
	oI6tKDmQVBp9SQBCz0gJOZdB/TuEI/tYlcCJUv3Q0yO90PPEqQgNMPFJNaxo9R2j
	Iq4uskLVjKRJ13Sr/2pBzqpOOolVHJqg5fHEELtdeaf6GyS5bfJY7eW8ceit4SUo
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=uTsAbX/uH6d7CaLQ17Apg5xv+Fw=; b=uujckahlzcjhLL8d6
	HLUHo7YqCZEvQfbYyxP4//bD7crK3AqrSClrfkuOemMZQjfgab1uut9hzz8GuwI0
	dKqlEobHy/hDiL/wKrO4ugX9TdtqKy74/DHZBoNw97AuHzAT84YgF6rsjoSgQQTC
	1mR6Hwyk9TfWyq3p1Uw9fU/GhA=
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
X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2
Message-ID: <521804D5.8010908@etr-usa.com>
Date: Fri, 23 Aug 2013 18:56:53 -0600
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
References: <52162CA9 DOT 9080002 AT etr-usa DOT com> <20130822171419 DOT GQ2562 AT calimero DOT vinschen DOT de> <CA+sc5mnedD0hOfzwTWYzy0QVhKC9gg-C68Nxfska-HG0HFOpLQ AT mail DOT gmail DOT com> <20130823094919 DOT GT2562 AT calimero DOT vinschen DOT de> <52178ED2 DOT 4090806 AT etr-usa DOT com> <5217A8A2 DOT 7060700 AT cygwin DOT com> <20130823191601 DOT GA1446 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20130823191601.GA1446@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 8/23/2013 13:16, Christopher Faylor wrote:
> 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.

I don't want this to end up being a bigger problem than the original 
behavior, either.

If you do end up deciding to block cross-Cygwin exec()s, shouldn't 
32-bit Cygwin refuse to run 64-bit Cygwin exes, too?

--
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