From: Dan Harkless <cygwin-list21@harkless.org>
To: cygwin@cygwin.com
Subject: Re: Is there any method to get 32bit Cygwin?
Date: Sat, 3 Dec 2022 06:56:24 -0800 [thread overview]
Message-ID: <d92e7e35-ef7e-f603-3f86-ac6dfbd5ba16@harkless.org> (raw)
In-Reply-To: <bf4bd78c-aec9-34da-154d-87164b95f4cf@harkless.org>
On 12/3/2022 6:48 AM, Dan Harkless via Cygwin wrote:
> On 12/3/2022 6:43 AM, LnH wrote:
> > That's what I did. I got the setup-x86.exe to the desktop. And then I run it and get the following error "Cygwin is not supported on 32-bit windows". However, I am running 64-bit windows.
>
> That's not what you said in your original mail. You said "when I try to
> update my 32-bit Cygwin using setup-x86-64". Again, you can't do that.
> And you need to use the commandline options that have been pointed out
> multiple times now. They're making it intentionally hard to install
> 32-bit Cygwin, because it's no longer supported. You need to read the
> instructions more carefully.
And if it's that you're trying to do an in-place upgrade of an existing
32-bit Cygwin installation to 64-bit, you can't do that either. AFAIAA,
you need to do a fresh 64-bit installation to a different tree, and then
copy your locally changed and locally created files from the old 32-bit
tree to the new 64-bit one.
--
Dan Harkless
http://harkless.org/dan/
next prev parent reply other threads:[~2022-12-03 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165047007.724080.1670063629607.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-12-03 10:33 ` Tatsuro MATSUOKA
2022-12-03 10:40 ` Takashi Yano
2022-12-03 12:09 ` Tatsuro MATSUOKA
2022-12-03 14:32 ` LnH
2022-12-03 14:38 ` Dan Harkless
2022-12-03 14:43 ` LnH
2022-12-03 14:48 ` Dan Harkless
2022-12-03 14:56 ` Dan Harkless [this message]
2022-12-03 15:02 ` LnH
2022-12-03 15:21 ` Oskar Skog
2022-12-03 15:27 ` LnH
2022-12-03 10:42 ` Dan Harkless
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=d92e7e35-ef7e-f603-3f86-ac6dfbd5ba16@harkless.org \
--to=cygwin-list21@harkless.org \
--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).