From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: isn't or hasn't 32 bit support going or gone away?
Date: Thu, 10 Nov 2016 10:18:00 -0000 [thread overview]
Message-ID: <20161110101840.GC24351@calimero.vinschen.de> (raw)
In-Reply-To: <e13670da-f3f3-2264-ebda-afcdb4a9f900@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Nov 10 02:55, Brian Inglis wrote:
> On 2016-11-10 02:16, Corinna Vinschen wrote:
> > On Nov 9 13:53, L. A. Walsh wrote:
> > > I thought I remember an announcement about 32-bit support
> > > going away in cygwin and that cygwin would only be built for
> > > 64-bit? Am I imagining this or was this reversed?
> >
> > We only (kind of) joked about it.
>
> MS will release that fix in an upcoming Anniversary Update, if
> the 32 bit MS Office Education and Enterprise licence revenue
> ever dwindles, and Insider devs' systems tell MS they don't do
> 32 bit builds.
Good thing MS doesn't collect user data...
> Cygwin won't have to worry about it, as they won't have a WoW
> to work on any more ;^>
I heard there are still lots of real 32 bit Vista/W7/W8.1/W10 systems
running, but I wonder what's the point. I won't actively pursue
dropping 32 bit, albeit getting rid of 32 bit would be a bit of a relief
in terms of ugly `#ifdef' handling in the code.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-10 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 21:53 L. A. Walsh
2016-11-10 9:16 ` Corinna Vinschen
2016-11-10 9:55 ` Brian Inglis
2016-11-10 10:18 ` Corinna Vinschen [this message]
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=20161110101840.GC24351@calimero.vinschen.de \
--to=corinna-cygwin@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).