public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: FAQ: fix Cygwin build requirements Date: Tue, 26 May 2020 17:15:44 +0000 (GMT) [thread overview] Message-ID: <20200526171544.672BF383E815@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=50d7dcaa0bd535a2a70e076a0ca0d15c1c1e8e01 commit 50d7dcaa0bd535a2a70e076a0ca0d15c1c1e8e01 Author: Corinna Vinschen <corinna@vinschen.de> Date: Tue May 26 19:15:37 2020 +0200 Cygwin: FAQ: fix Cygwin build requirements Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/doc/faq-programming.xml | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index 65bfed97e..5920ca8c4 100644 --- a/winsup/doc/faq-programming.xml +++ b/winsup/doc/faq-programming.xml @@ -676,16 +676,20 @@ rewriting the runtime library in question from specs... <answer> <para>First, you need to make sure you have the necessary build tools -installed; you at least need <literal>gcc-g++</literal>, <literal>make</literal>, -<literal>perl</literal>, <literal>cocom</literal>, <literal>gettext-devel</literal>, -<literal>libiconv-devel</literal> and <literal>zlib-devel</literal>. +installed; you at least need <literal>gcc-g++</literal>, +<literal>make</literal>, <literal>patch</literal>, <literal>perl</literal>, +<literal>gettext-devel</literal>, <literal>libiconv-devel</literal> and +<literal>zlib-devel</literal>. Installing <literal>git</literal> to fetch +the sources from the +<ulink url="https://cygwin.com/git/newlib-cygwin.git">source repository</ulink> +helps, too. 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>. Building for 32-bit Cygwin also requires -<literal>mingw64-x86_64-gcc-core</literal> (for building the cyglsa64 DLL for WoW64), <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>. -If you want to run the tests, <literal>dejagnu</literal> is also required. +<!-- If you want to run the tests, <literal>dejagnu</literal> is also required. --> Normally, building ignores any errors in building the documentation, which requires the <literal>dblatex</literal>, <literal>docbook2X</literal>, <literal>docbook-xml45</literal>, <literal>docbook-xsl</literal>, and
reply other threads:[~2020-05-26 17:15 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=20200526171544.672BF383E815@sourceware.org \ --to=corinna@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).