public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Denis Excoffier <cygwin@Denis-Excoffier.org>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Errors in building the documentation prevent compilation from completing properly
Date: Thu, 20 Oct 2022 11:29:39 +0100	[thread overview]
Message-ID: <ee940ded-db00-2543-0de8-552e2c40c30b@dronecode.org.uk> (raw)
In-Reply-To: <FD4CA95F-913A-44F3-97C9-7AD076E8A991@Denis-Excoffier.org>

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'.

[1] 
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=f4a26ececa180cec70c41b6dd2082ff730f92065

> 
> However, in order to 'make' and then 'make install' properly, i had to apply the following
> easy patch (below).
> 
> Hope this helps,
> 
> Regards,
> 
> Denis Excoffier.
> 
> 
> diff -uNr o/newlib-cygwin/winsup/doc/Makefile.am p/newlib-cygwin/winsup/doc/Makefile.am
> --- o/newlib-cygwin/winsup/doc/Makefile.am	2022-09-05 13:09:51.000000000 +0200
> +++ p/newlib-cygwin/winsup/doc/Makefile.am	2022-10-19 14:00:03.052557100 +0200
> @@ -61,7 +61,7 @@
>   
>   install-info-local: cygwin-ug-net.info cygwin-api.info
>   	@$(MKDIR_P) $(DESTDIR)$(infodir)
> -	$(INSTALL_DATA) *.info* $(DESTDIR)$(infodir)
> +	-$(INSTALL_DATA) *.info* $(DESTDIR)$(infodir)

Ignoring errors here is (and always was) a terrible idea, frankly.

>   
>   install-etc:
>   	@$(MKDIR_P) $(DESTDIR)$(sysconfdir)/postinstall
> @@ -141,7 +141,7 @@
>   
>   # this generates a custom charmap for docbook2x-texi which has a mapping for &reg;
>   charmap:
> -	cp /usr/share/docbook2X/charmaps/texi.charmap charmap
> +	-cp /usr/share/docbook2X/charmaps/texi.charmap charmap
>   	echo "ae (R)" >>charmap
>   
>   intro2man.stamp: intro.xml man.xsl


  reply	other threads:[~2022-10-20 10:29 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 [this message]
2022-10-20 17:46   ` Denis Excoffier
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=ee940ded-db00-2543-0de8-552e2c40c30b@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@Denis-Excoffier.org \
    --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).