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=ykv6e+9pCSh1LJVWrF3zq3CmU6xHohuZiIEAz/3jrot
	/y+D5QXXzXezFowCOkr/tBmVD5Up4TIowWRAvj/04sO32aJ+oDmcCME6XxdcNHN2
	+VLfZkAKtrdteNEWew1cn4ZsIqcQIOsjLHYkBTjlrvRk15RMT6AdWI85aOVtqLgI
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51F368C4.5030309@etr-usa.com>
Date: Sat, 27 Jul 2013 00:29:24 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: please update the supported Cygwin package list to be distinct for 32-bit, 64-bit or both; and help on how install both in a merged fashion
References: <CADex0xxLK3LRfHcat8UYXDUoYxRu5OPzV0_+FXMKd7k_J4G+Vg@mail.gmail.com>	<51F34FA0.50300@gmail.com> <CADex0xwDTvHaOS-_xAr3pARiBQ19zAdOS8US06r+E14b65SC-w@mail.gmail.com> <51F35E4A.4040207@gmail.com>
In-Reply-To: <51F35E4A.4040207@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/26/2013 23:44, marco atzeri wrote:
> Il 7/27/2013 7:17 AM, Kenneth Wolcott ha scritto:
>>
>>    I guess I will somehow modify my PATH so that I have
>> /cygdrive/c/cygwin64/usr/bin and /cygdrive/c/cygwin32/usr/bin
>
> mixing will not work as the dll's are called in the same way

Just to emphasize: if both 32- and 64-bit Cygwin bin dirs are in your 
PATH at the same time, you will get complaints in the terminal window 
every time you try to run a 32-bit Cygwin program while in a 64-bit 
mintty shell, or vice versa.

The most likely reason this will happen is that the package set in both 
Cygwins isn't the same.

This could be fixed, but it wouldn't be trivial:

1. Rename the 64-bit cygwin1.dll; say, cygwin2.dll.  (It's not that wild 
an idea.  The ABI *is* different between 32- and 64-bit versions.)

2. Teach setup.exe how to install packages of both bitnesses at the same 
time.  You'd end up with something like many Linuxes: /bin and /bin64, 
/lib and /lib64.

3. Teach cygport how to build and configure both bitnesses at the same 
time.  This is nontrivial in itself.

Having done all that, you still don't end up with a completely 
integrated pair of Cygwins, since they aren't going to have any shared 
in-memory data structures.  (Separate cygheaps.)  You couldn't pass a 
file handle from a 32-bit Cygwin program to a 64-bit Cygwin program, for 
example.

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