public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin] Update FAQ listing required packages for building Cygwin
Date: Tue, 28 Jun 2016 19:11:00 -0000 [thread overview]
Message-ID: <20160628191142.53900.qmail@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=24b1c901169d34410e209b75e79b732838325f5f
commit 24b1c901169d34410e209b75e79b732838325f5f
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Mon Jun 27 17:32:35 2016 +0100
Update FAQ listing required packages for building Cygwin
docbook2X is now required for building documentation
libiconv differences between x86_64 and x86 no longer exist
Diff:
---
winsup/doc/faq-programming.xml | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index 3aa773a..1f595f8 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -680,17 +680,16 @@ rewriting the runtime library in question from specs...
<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</literal>, <literal>gettext-devel</literal>,
-and <literal>zlib-devel</literal>.
-Building for 32-bit Cygwin also requires <literal>libiconv</literal>,
-<literal>mingw64-i686-gcc-g++</literal>, <literal>mingw64-i686-zlib</literal>,
-and <literal>mingw64-x86_64-gcc-core</literal>.
-Building for 64-bit Cygwin also requires <literal>libiconv-devel</literal>,
-<literal>mingw64-x86_64-gcc-g++</literal>, and
+<literal>perl</literal>, <literal>cocom</literal>, <literal>gettext-devel</literal>,
+<literal>libiconv-devel</literal> and <literal>zlib-devel</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
+<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.
Normally, building ignores any errors in building the documentation,
-which requires the <literal>dblatex</literal>,
+which requires the <literal>dblatex</literal>, <literal>docbook2X</literal>,
<literal>docbook-xml45</literal>, <literal>docbook-xsl</literal>, and
<literal>xmlto</literal> packages. For more information on building the
documentation, see the README included in the <literal>cygwin-doc</literal> package.
reply other threads:[~2016-06-28 19:11 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=20160628191142.53900.qmail@sourceware.org \
--to=jturney@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: 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).