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
This commit is contained in:
parent
9193f6efde
commit
b441bad182
|
@ -346,7 +346,7 @@ would be difficult.
|
||||||
<question><para>Where is Objective C?</para></question>
|
<question><para>Where is Objective C?</para></question>
|
||||||
<answer>
|
<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; resulting binaries will depend on the <literal>libobjc2</literal>
|
||||||
package at runtime.
|
package at runtime.
|
||||||
</para>
|
</para>
|
||||||
|
@ -684,8 +684,6 @@ installed; you at least need <literal>gcc-g++</literal>,
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<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
|
Building for 64-bit Cygwin also requires
|
||||||
<literal>mingw64-x86_64-gcc-g++</literal> and
|
<literal>mingw64-x86_64-gcc-g++</literal> and
|
||||||
<literal>mingw64-x86_64-zlib</literal>.
|
<literal>mingw64-x86_64-zlib</literal>.
|
||||||
|
|
|
@ -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
|
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
|
connection, and the system will not be required for any other purpose for
|
||||||
many hours (or days) until installation completes.
|
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>
|
</para>
|
||||||
</answer></qandaentry>
|
</answer></qandaentry>
|
||||||
|
|
||||||
|
|
|
@ -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>
|
<question><para>What versions of Windows are supported?</para></question>
|
||||||
<answer>
|
<answer>
|
||||||
|
|
||||||
<para>Cygwin can be expected to run on all modern, released versions of Windows,
|
<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
|
This includes Windows 7, Windows Server 2008 R2 and all later versions of
|
||||||
later versions of Windows, except Windows S mode due to its limitations.
|
Windows, except Windows S mode due to its limitations, on 64 bit AMD/Intel
|
||||||
The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on
|
compatible PCs, and under x64 emulation on ARM PCs running Windows 11.</para>
|
||||||
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>Keep in mind that Cygwin can only do as much as the underlying OS
|
<para>Keep in mind that Cygwin can only do as much as the underlying OS
|
||||||
supports. Because of this, Cygwin will behave differently, and
|
supports. Because of this, Cygwin will behave differently, and
|
||||||
exhibit different limitations, on the various versions of Windows.
|
exhibit different limitations, on the various versions of Windows.
|
||||||
|
|
Loading…
Reference in New Issue