public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Design mixed 32 and 64 bit systems.
Date: Wed, 27 Nov 2013 22:27:00 -0000	[thread overview]
Message-ID: <20131127222714.GB3055@ednor.casa.cgf.cx> (raw)
In-Reply-To: <52966F74.4040104@gmail.com>

On Thu, Nov 28, 2013 at 06:17:24AM +0800, JonY wrote:
>On 11/28/2013 04:11, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> Technically, the following is off topic for this list.  But because
>> it is about what appears to me as a done deal - something that is too
>> late to change - I thought it might be off-topic for the main list.
>> We can move it there if you feel that appropriate.
>> 
>> As I understand it, 32 bit and 64 bit have to be in different directory
>> trees, e.g., C:\cygwin and C:\cygwin64.  As I understand it, that
>> is because they both look for /bin/cygwin1.dll and avoid getting the
>> wrong one by having different root directories.
>> 
>
>Windows will spick the correct bitness if you have both in PATH. This is
>not the case if you somehow managed to install 64bit Cygwin on 32bit
>Windows, in which case you deserve the error :)
>
>> My question is why 64 bit wasn't named cygwin2.dll?  32 bit would
>> be version 1.7.25 and the corresponding 64 bit version would be
>> 2.7.25.  Could that have allowed a single, mixed, transitional,
>> 64-except-32-when-no-64 installation?
>> 
>
>Why? It is built from exactly the same sources, it is also the first
>version on 64bit Windows. Not to mention many programs hardcoded to load
>"cygwin1.dll" dynamically.

And, even if we had put a "cygwin2.dll" in /bin, there would still be
conflicts with the program names of all of the other programs in /bin.

cgf

  reply	other threads:[~2013-11-27 22:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 20:13 Buchbinder, Barry (NIH/NIAID) [E]
2013-11-27 22:17 ` JonY
2013-11-27 22:27   ` Christopher Faylor [this message]
2013-12-02 19:35 ` Warren Young
2013-12-02 19:56   ` Christopher Faylor
2013-12-02 20:30     ` Warren Young
2013-12-02 20:44       ` Warren Young
2013-12-02 21:07       ` Christopher Faylor
2013-12-17 20:41         ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131127222714.GB3055@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).