From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: Jon Turney <jon.turney@dronecode.org.uk>, cygwin@cygwin.com
Cc: Denis Excoffier <cygwin@Denis-Excoffier.org>
Subject: Re: Errors in building the documentation prevent compilation from completing properly
Date: Thu, 20 Oct 2022 19:46:04 +0200 [thread overview]
Message-ID: <426C8E9E-A69A-4744-AB45-440AB76190ED@Denis-Excoffier.org> (raw)
In-Reply-To: <ee940ded-db00-2543-0de8-552e2c40c30b@dronecode.org.uk>
> On 2022-10-20 12:29, Jon Turney wrote:
>
> On 19/10/2022 18:57, Denis Excoffier wrote:
>> Hello,
>> Currently i have docbook2X not working on my system (a perl problem
>> that i don't know how to repair, but in a few months i will reinstall completely
>> this C:\Cygwin64 which dates back to 2019).
>> This means that /usr/share/docbook2X and /usr/bin/docbook2x-texi are missing.
>> Consequently, no *.info* file is produced.
>> Nevertheless, i tried to compile cygwin from sources (newlib-cygwin-3.3.6.tar.bz2),
>> knowing that "Normally, building ignores any errors in building the documentation"
>> (see https://cygwin.com/faq.html#faq.programming.building-cygwin)
>
> The behaviour was changed by [1], but unfortunately the documentation change that contains has not yet been published.
>
> Use the configure option '--disable-doc'.
For me, '--disable-doc' makes no difference with the unpatched code. Same errors. Sorry.
Regards,
Denis Excoffier.
next prev parent reply other threads:[~2022-10-20 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 17:57 Denis Excoffier
2022-10-20 10:29 ` Jon Turney
2022-10-20 17:46 ` Denis Excoffier [this message]
2022-11-15 3:24 ` Denis Excoffier
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=426C8E9E-A69A-4744-AB45-440AB76190ED@Denis-Excoffier.org \
--to=cygwin@denis-excoffier.org \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).