This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 23 Aug 2013 23:06:07 -0400
- 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> <521804D5 dot 8010908 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
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