public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 64-bit vs. 32-bit
Date: Fri, 25 Apr 2014 17:38:00 -0000	[thread overview]
Message-ID: <20140425173837.GC346@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CABn7SNaxsvGXsEjkQM6csfpbnBRRhds6g6ajQSy=MwErSLkx1A@mail.gmail.com>

On Fri, Apr 25, 2014 at 01:26:22PM -0400, Tom Szczesny wrote:
>I have a 64-bit Windows laptop, and installed Cygwin several years ago.
>I wish to verify that I did install the 64-bit installation.
>I get the following results:
>
>cygcheck -V
>cygcheck (cygwin) 1.7.15
>
>uname
>CYGWIN_NT-6.1-WOW64
>
>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)?

1) No, you didn't install a 64-bit version of Cygwin.  "uname -a" should
make that clear.  You'll need to instal a 64-bit version if that's what
you want.

2) Cygwin doesn't build Linux apps.  If you have a cross-compiler then
it won't automatically decide to build 64-bit Linux apps because you
are on a 64-bit sytem.

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

  reply	other threads:[~2014-04-25 17:38 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 [this message]
2014-04-25 17:47   ` Tim Prince
2014-04-25 21:44 ` Warren Young
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=20140425173837.GC346@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.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).