public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
Cc: Jon Turney <>
Subject: [PATCH] cygwin: Add cocom and patch to build prerequisites in FAQ
Date: Sat, 18 Dec 2021 17:47:48 +0000	[thread overview]
Message-ID: <> (raw)

Add patch, and make cocom unconditional in list of build prerequisites.

Even though the products of these tools are checked in, these are tools
are required when building in a fresh git checkout, presumably due to
the order in which git creates the files resulting in timestamps which
indicate that the output of rules using these tools is more recent than
the input.


Also drop a duplicate sentence about 'fetch sources from git'.
 winsup/doc/faq-programming.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index 46dd23ab8..3c6bf7b46 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -679,11 +679,11 @@ rewriting the runtime library in question from specs...
 installed; you at least need <literal>gcc-g++</literal>,
 <literal>make</literal>, <literal>automake</literal>,
 <literal>autoconf</literal>, <literal>git</literal>, <literal>perl</literal>,
-<literal>gettext-devel</literal>, <literal>libiconv-devel</literal> and
-<literal>zlib-devel</literal>.  Fetch the sources from the
-<ulink url="">Cygwin GIT source repository</ulink>.
-If you change a certain core part of Cygwin, namely the layout
-of the Cygwin TLS area, you also have to install <literal>cocom</literal>.
+<literal>gettext-devel</literal>, <literal>libiconv-devel</literal>
+<literal>zlib-devel</literal>, <literal>cocom</literal> and <literal>patch</literal>.
 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

                 reply	other threads:[~2021-12-18 17:48 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).