public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space)
Date: Fri, 12 Jan 2018 20:20:00 -0000	[thread overview]
Message-ID: <0DB190A7-5951-42D4-9EA9-A37E807EEC29@solidrocksystems.com> (raw)
In-Reply-To: <c5811365-3b30-5cd6-e4fe-c72fd26d618d@cygwin.com>

> On Jan 12, 2018, at 12:11 PM, Yaakov Selkowitz wrote:
> 
> On 2018-01-12 03:13, Corinna Vinschen wrote:
>> On Jan 11 22:52, Denis Excoffier wrote:
>>> The full list contains 8006 lines, i have the complete Cygwin 32bit installation
>> 
>> The bottom line of this is, and it has been said before and I can't
>> stress this enough, we can't support this scenario at all, for the
>> simple fact that we have more DLLs than fit into the 32 bit address
>> space.  It's not much of a problem on 64 bit, but on 32 bit it's just
>> not feasible anymore.
>> 
>> Ultimately, You should (must) not install all of Cygwin on 32 bit, only
>> the set of stuff you need on top of the base category.  Or install 64
>> bit Cygwin.
> 
> If it is not possible for the entire 32-bit distribution to function as
> a whole, is it time to reconsider how much we provide for 32-bit?  And
> when can we just drop 32-bit entirely?

I have no dog in this hunt: I'm currently 64-bit (Windows and Cygwin). Having said that…

I think this is an extreme reaction. 32-bit Windows isn't going away anytime soon (as in not in the next five and probably more like ten years). There's nothing wrong with Cygwin-32. No one* needs to install all of Cygwin (And for those running 32-bit Cygwin on a 64-bit Windows, a giant rhetorical WHY?!?!). For many (most?) of us who use a relatively small part of Cygwin, there is no issue with the 32-bit address space. (I never had a problem when I ran 32-bit, which I did through last year (on a 32-bit Windows.)

For those that install everything out of laziness, well, that's not going to work anymore (and, from reports, hasn't worked very well for quite some time). But that's no reason to punish everyone else. There's also no reason to stop creating 32-bit packages. 32-bit Windows has limited address space. This isn't new, and it isn't news. If you run out of space, you run out of space. Switch to 64-bit or do without something. But it's not a reason to force everyone (on 32-bit windows) to do without everything.


*Within three decimal points.
--
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

  parent reply	other threads:[~2018-01-12 20:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 12:31 rebase-4.4.3-1 regression: Too many DLLs for available address space Christian Franke
2018-01-11 16:06 ` Corinna Vinschen
2018-01-11 17:53   ` Achim Gratz
2018-01-11 17:56   ` Corinna Vinschen
2018-01-11 21:52 ` Denis Excoffier
2018-01-12  9:13   ` Corinna Vinschen
2018-01-12 18:11     ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Yaakov Selkowitz
2018-01-12 19:02       ` Future of 32-bit distro Brian Inglis
2018-01-12 19:33         ` Keith Christian
     [not found]           ` <7218003ac95dc6814bbb309dda3df748@smtp-cloud8.xs4all.net>
2018-01-13  1:56             ` Brian Inglis
2018-01-13  2:15               ` Keith Christian
2018-01-12 19:40         ` Steven Penny
2018-01-12 20:20       ` Vince Rice [this message]
2018-01-12 22:00         ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Keith Christian
2018-01-13  9:11       ` Future of 32-bit distro David Stacey
2018-01-12 17:16 ` rebase-4.4.3-1 regression: Too many DLLs for available address space Thomas Waldmann

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=0DB190A7-5951-42D4-9EA9-A37E807EEC29@solidrocksystems.com \
    --to=vrice@solidrocksystems.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).