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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=QOhmTLmQQT3hppNlwRpPTP94K5sTvTtnAi+ncTQ1ohKpiAdnw9aLm
	LxU2WSaEBcS256P4mbeeIkqetZPmwVd5TpOtw2pnyCl7vIefe25a+9iueQOhlh6q
	OVktmDl+aJP8NYqmNQWYIjhXaVYr1hc7himunekjUsujDT8UiEhZ34=
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=AdIQxHrHtJ7sHXTn91NgyjF5aRs=; b=LKjH+5bChlqFOPLZX0HC8KnLpmEe
	EC+B/K9zhiZnMozhhOvZfy5rrzwS3ZYjuiIyS1puO75KbWyQAnOEVKpvo8TsPyJF
	PeqCtCJ9gmwL22rGzh6B1a9n3gFXFf3CUFGWqUf4KkppX0UoPCDn/MoFB33FtXLo
	OkEg9tuA8LwCLv0=
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=-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 AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18S6otTgVyHbFlbm3P7T7pt
Date:	Fri, 23 Aug 2013 23:06:07 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
Message-ID:	<20130824030607.GA3625@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
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> <521804D5 DOT 8010908 AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<521804D5.8010908@etr-usa.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Fri, Aug 23, 2013 at 06:56:53PM -0600, Warren Young wrote:
>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.

How would that end up being a bigger problem?  It's basically just a
different error message with a way to turn it on and off.

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

"and vice versa"

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

- Raw text -