public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Cygwin 32 doc build failure
Date: Thu, 23 Dec 2021 14:39:47 -0500	[thread overview]
Message-ID: <5e22ec07-b527-48df-c06c-5296a6c46e70@cornell.edu> (raw)
In-Reply-To: <615a7e60-922a-8e67-70ed-fbbb3c002bcd@SystematicSw.ab.ca>

On 12/23/2021 12:35 PM, Brian Inglis wrote:
> Building cygwin 32 doc (with latest packages, git sources, after running 
> winsup/autogen.sh) get the following doc build failure (not on cygwin 64 - all 
> builds okay) - anyone seen this before and any clue where to look?
> 
> $ ../configure && make
> ...
> Making all in doc
> make[3]: Entering directory 
> '$HOME/src/cygwin/newlib-cygwin/build32/i686-pc-cygwin/winsup/doc'
> xmlto --skip-validation --with-dblatex pdf -o cygwin-ug-net/ -m 
> ../../../../winsup/doc/fo.xsl ../../../../winsup/doc/cygwin-ug-net.xml
> Traceback (most recent call last):
>    File "/usr/bin/dblatex", line 3, in <module>
>      from dbtexmf.dblatex import dblatex
> ModuleNotFoundError: No module named 'dbtexmf'

It looks like dblatex needs python3.8.  Does your 32-bit installation have 
python3 pointing to python3.8?

$ /usr/sbin/alternatives.exe --display python3
python3 - status is auto.
  link currently points to /usr/bin/python3.8
/usr/bin/python3.8 - priority 38
Current `best' version is /usr/bin/python3.8.

Ken

  reply	other threads:[~2021-12-23 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 17:35 Brian Inglis
2021-12-23 19:39 ` Ken Brown [this message]
2021-12-23 19:54   ` Marco Atzeri

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=5e22ec07-b527-48df-c06c-5296a6c46e70@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).