From: Oskar Skog <novia@oskog97.com>
To: cygwin@cygwin.com
Subject: Build instructions in the FAQ
Date: Sun, 5 Dec 2021 12:38:46 +0200 [thread overview]
Message-ID: <5ed09ba4-1614-ad4b-0e4e-a1786d89451a@oskog97.com> (raw)
I have recently tested a small patch. The build instructions in the
FAQ kind of worked. I think the list of prerequisite packages could be
a bit more clear.
https://cygwin.com/faq/faq.html#faq.programming.building-cygwin
The FAQ forgot to mention that `patch` is required.
`cocom` is also required for the `shilka` command, but the wording made
me think it wasn't required (I don't think I've changed the Cygwin TLS).
Also, make didn't say it ignored any errors when it tried to make the
documentation, so I installed those packages too, and it's still missing
some LaTeX package. Luckily, `make install` worked "fine" after the
failed `make`.
TL;DR I tried only installing the bare minimum of packages for building
Cygwin but had to install all of them just to be sure.
I don't think the patch I tried would have affected the TLS area:
https://cygwin.com/pipermail/cygwin/2021-December/250118.html
reply other threads:[~2021-12-05 10:38 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=5ed09ba4-1614-ad4b-0e4e-a1786d89451a@oskog97.com \
--to=novia@oskog97.com \
--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).