From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin-talk@cygwin.com" <cygwin-talk@cygwin.com>
Subject: Design mixed 32 and 64 bit systems.
Date: Wed, 27 Nov 2013 20:13:00 -0000 [thread overview]
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA21D7054@MLBXV06.nih.gov> (raw)
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.
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?
Remember that I'm not a programmer and everything that I think that
I've learned about this topic I've picked up by read the cygwin
and cygwin-apps mailing lists. So this is for my education and no
response is necessary.
Tomorrow, Cygwin and the community that supports it will be on my
list of things that I'm thankful for.
TIA,
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
next reply other threads:[~2013-11-27 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 20:13 Buchbinder, Barry (NIH/NIAID) [E] [this message]
2013-11-27 22:17 ` JonY
2013-11-27 22:27 ` Christopher Faylor
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=6CF2FC1279D0844C9357664DC5A08BA21D7054@MLBXV06.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--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).