public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Update FAQs for removal of 32-bit Cygwin Date: Tue, 12 Jul 2022 13:00:07 +0000 (GMT) [thread overview] Message-ID: <20220712130007.D59B03858C50@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=b441bad1827378cd31f265c795e99aae70a86941 commit b441bad1827378cd31f265c795e99aae70a86941 Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Fri Jul 1 15:20:42 2022 +0100 Update FAQs for removal of 32-bit Cygwin Update FAQs for removal of 32-bit Cygwin Also update FAQs for dropping support for Windows Vista/Server 20008 Diff: --- winsup/doc/faq-programming.xml | 4 +--- winsup/doc/faq-setup.xml | 3 --- winsup/doc/faq-what.xml | 12 +++++------- 3 files changed, 6 insertions(+), 13 deletions(-) diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index 3c6bf7b46..c2c4004c1 100644 --- a/winsup/doc/faq-programming.xml +++ b/winsup/doc/faq-programming.xml @@ -346,7 +346,7 @@ would be difficult. <question><para>Where is Objective C?</para></question> <answer> -<para>Support for compiling Objective C is available in the <literal>gcc{4}-objc</literal> +<para>Support for compiling Objective C is available in the <literal>gcc-objc</literal> package; resulting binaries will depend on the <literal>libobjc2</literal> package at runtime. </para> @@ -684,8 +684,6 @@ installed; you at least need <literal>gcc-g++</literal>, </para> <para> -Building for 32-bit Cygwin also requires -<literal>mingw64-i686-gcc-g++</literal> and <literal>mingw64-i686-zlib</literal>. Building for 64-bit Cygwin also requires <literal>mingw64-x86_64-gcc-g++</literal> and <literal>mingw64-x86_64-zlib</literal>. diff --git a/winsup/doc/faq-setup.xml b/winsup/doc/faq-setup.xml index cfa771098..ce1069616 100644 --- a/winsup/doc/faq-setup.xml +++ b/winsup/doc/faq-setup.xml @@ -383,9 +383,6 @@ are strongly advised not to attempt to at once, unless you have a lot of free disk space, a very high speed network connection, and the system will not be required for any other purpose for many hours (or days) until installation completes. -For a 32-bit Cygwin installation, you can not install everything, as the -installation will fail because the 4GB memory available is insufficient to allow -all the DLLs required to run along with the programs using them. </para> </answer></qandaentry> diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index 77ba1c5fd..4bdbf4eff 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,13 +30,11 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. <question><para>What versions of Windows are supported?</para></question> <answer> -<para>Cygwin can be expected to run on all modern, released versions of Windows, -from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all -later versions of Windows, except Windows S mode due to its limitations. -The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on -released 64 bit versions of Windows including ARM PCs, -the 64 bit version of course only on 64 bit AMD/Intel compatible PCs. -</para> +<para>Cygwin can be expected to run on all modern, released versions of Windows. +This includes Windows 7, Windows Server 2008 R2 and all later versions of +Windows, except Windows S mode due to its limitations, on 64 bit AMD/Intel +compatible PCs, and under x64 emulation on ARM PCs running Windows 11.</para> + <para>Keep in mind that Cygwin can only do as much as the underlying OS supports. Because of this, Cygwin will behave differently, and exhibit different limitations, on the various versions of Windows.
reply other threads:[~2022-07-12 13:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220712130007.D59B03858C50@sourceware.org \ --to=jturney@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ /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: linkBe 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).