From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: 64-bit vs. 32-bit
Date: Fri, 25 Apr 2014 21:44:00 -0000 [thread overview]
Message-ID: <535AD731.8040809@etr-usa.com> (raw)
In-Reply-To: <CABn7SNaxsvGXsEjkQM6csfpbnBRRhds6g6ajQSy=MwErSLkx1A@mail.gmail.com>
On 4/25/2014 11:26, Tom Szczesny wrote:
>
> CYGWIN_NT-6.1-WOW64
"WOW64" means 32-bit Windows emulated on top of 64-bit Windows.[1] This
tells you that Cygwin is running inside that 32-bit environment.
> If I did install the 64-bit version, when I rebuild my Linux app on
> Cygwin, do I automatically get a 64-bit executable (that will not run
> on a 32-bit Windows computer)?
You actually have to go out of your way to get a 32-bit executable when
running 64-bit Cygwin, and vice versa. So yes, if you install 64-bit
Cygwin, you don't have to worry about accidentally getting 32-bit
executables.
You don't have to guess and hope, though. From 32-bit Cygwin:
$ file /bin/ls
/bin/ls: PE32 executable (console) Intel 80386 (stripped to
external PDB), for MS Windows
$ file /cygdrive/c/cygwin64/bin/ls
/cygdrive/c/cygwin64/bin/ls: PE32+ executable (console) x86-64, for
MS Windows
file(1) saith sooth what what form of executable thou hast wrought.
You might also find this piece enlightening: http://goo.gl/qv5ki7
[1] http://goo.gl/uGmKYv
--
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
next prev parent reply other threads:[~2014-04-25 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:26 Tom Szczesny
2014-04-25 17:38 ` Christopher Faylor
2014-04-25 17:47 ` Tim Prince
2014-04-25 21:44 ` Warren Young [this message]
2014-04-25 22:29 ` Chris J. Breisch
2014-04-25 18:13 Tom Szczesny
2014-04-25 18:21 ` Erwin Waterlander
2014-04-25 19:15 ` 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=535AD731.8040809@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@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).