From: Eliot Moss <moss@cs.umass.edu>
To: Andy Romens <Romens.Andy@hotmail.com>,
Stephen John Smoogen <smooge@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Questions on how to upgrade Apache
Date: Thu, 8 Apr 2021 11:57:19 -0400 [thread overview]
Message-ID: <4e6cdeb2-51f9-31f2-7363-3c935bb869d5@cs.umass.edu> (raw)
In-Reply-To: <CH0PR14MB4930B3C41EE5CC1D23C8145AFB749@CH0PR14MB4930.namprd14.prod.outlook.com>
On 4/8/2021 11:49 AM, Andy Romens via Cygwin wrote:
> Is there something else Cygwin provides that I should use instead of Apache?
> Sorry for the elementary questions, I’m still quite new to this :)
No. Cygwin, at its heart, is a Windows library (.dll file) that, when used,
provides a library call environment as close to POSIX (Linux, Unix) as it can,
given that Windows is not Unix. Programs must be explicitly compiled to use
that library. Sometimes that need adjustments (patches) to work correctly in
the environment. Presumably all those patches that would be necessary for
previous version so Apache are in the source package for those previous
versions, and might be enough for building a new version as well. As you are
probably aware, a number of commonly used Unix programs have been ported to
work under Cygwin.
Alternatively, you can use Windows-native programs and tools. I personally am
not sure if Apache is available as a Windows-native download, etc.
There is also the Windows Subsystem for Linux, which runs a virtual machine
under which many Unix programs can be installed without modification.
Regards - Eliot Moss
next prev parent reply other threads:[~2021-04-08 15:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:34 Andy Romens
2021-04-06 20:37 ` Andy Romens
2021-04-08 5:30 ` Andrey Repin
2021-04-09 0:26 ` Brian S. Wilson
2021-04-08 13:22 ` Andy Romens
2021-04-08 14:33 ` Stephen John Smoogen
2021-04-08 15:49 ` Andy Romens
2021-04-08 15:57 ` Eliot Moss [this message]
2021-04-08 16:37 ` René Berber
2021-04-08 18:33 ` Glenn Strauss
2021-04-08 19:53 ` bzs
2021-04-09 6:23 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-04-09 9:08 ` Csaba Raduly
2021-04-09 11:59 ` Brian S. Wilson
2021-04-09 14:46 ` Brian Inglis
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=4e6cdeb2-51f9-31f2-7363-3c935bb869d5@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=Romens.Andy@hotmail.com \
--cc=cygwin@cygwin.com \
--cc=smooge@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).