From: Jon Turney <jon.turney@dronecode.org.uk>
To: Olivier Souan <osouan@gmail.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: 32-bit setup-x86.exe missing on cygwin.com
Date: Tue, 6 Dec 2022 19:58:30 +0000 [thread overview]
Message-ID: <a375bda2-ed5d-e129-d009-710a8eec89e2@dronecode.org.uk> (raw)
In-Reply-To: <CADkAsXDMhPC0LMaZnaWcCQOBovWimFQoezVRy_9Fz45nStOfng@mail.gmail.com>
On 06/12/2022 01:32, Olivier Souan via Cygwin wrote:
> Hello,
>
> I am an enthusiastic user of Cygwin since a few years but now I cannot
> download a functioning 32-bit setup-x86.exe from cygwin.com.
>
> Indeed, the webpage "https://www.cygwin.com/install.html" reads:
>
> "About 32 bit Cygwin
> The limited address space of 32 bit Windows means that random failures
> in the fork(2) system call are more likely. Therefore, we recommend
> using 32 bit Cygwin only in limited scenarios, with only a minimum of
> necessary packages installed, and only if there's no way to run 64 bit
> Cygwin instead.
> You have been warned. If you're still sure you really need a 32 bit
> Cygwin, and there's absolutely no way around it, you may run the
> setup-x86.exe [link to https://www.cygwin.com/setup-x86.exe]
> installer.
I've added the words "following the instructions above." to this sentence.
> If 32-bit support is really not possible, would that be at least
> possible either to:
>
> 1) Offer a truly functioning 32-bit version of setup-x86.exe, distinct
> from setup-x86_64.exe, or
> 2) Open a legacy 32-bit download site where all the 32-bit compliant
> packages would be stored.
This announcement may be of interest to you:
https://cygwin.com/pipermail/cygwin-announce/2022-November/010810.html
If you still have difficulty installing x86 Cygwin, or find the
instructions unclear, please let us know.
prev parent reply other threads:[~2022-12-06 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 1:32 Olivier Souan
2022-12-06 2:01 ` Takashi Yano
2022-12-06 4:52 ` LnH
2022-12-06 19:58 ` Jon Turney [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=a375bda2-ed5d-e129-d009-710a8eec89e2@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=osouan@gmail.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).