From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12401 invoked by alias); 27 Jul 2013 06:29:37 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12391 invoked by uid 89); 27 Jul 2013 06:29:37 -0000 X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RDNS_NONE autolearn=no version=3.3.1 Received: from Unknown (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 27 Jul 2013 06:29:36 +0000 Received: (qmail 63331 invoked by uid 13447); 27 Jul 2013 06:29:28 -0000 Received: from unknown (HELO [172.20.0.42]) ([107.4.26.51]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 27 Jul 2013 06:29:28 -0000 Message-ID: <51F368C4.5030309@etr-usa.com> Date: Sat, 27 Jul 2013 07:57:00 -0000 From: Warren Young 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 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: <51F34FA0.50300@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 X-SW-Source: 2013-07/txt/msg00619.txt.bz2 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