From: Tom Holaday <tlholaday@gmail.com>
To: git@vger.kernel.org
Subject: git doc build failure on OS X 10.5.6 (Leopard) during docbook2x-texi phase
Date: Thu, 12 Mar 2009 08:22:29 -0400 [thread overview]
Message-ID: <5e68abd90903120522q635e41f9j118e74158ab04524@mail.gmail.com> (raw)
(Thanks Jay Soffian for the environment variables)
The commands ...
$ export ASCIIDOC8=YesPlease
$ export DOCBOOK_XSL_172=YesPlease
$ make prefix=/usr/local all doc info
... terminate with these errors:
/bin/sh: docbook2x-texi: command not found [ x 147 ]
... this warning:
gitman.texi:4: warning: unrecognized encoding name `UTF-8'.
and a zero-length user-manual.texi in Documentation.
Upon investigation, I determined that ...
$ which docbook2x-texi
... reports empty, but ...
$ which docbook2texi
... reports /opt/local/bin/docbook2texi.
$ docbook2texi --version
/opt/local/bin/docbook2texi (part of docbook2X 0.8.8)
$Revision: 1.12 $ $Date: 2006/04/14 17:29:04 $
<URL:http://docbook2x.sourceforge.net/>
Is docbook2texi vs docbook2x-texi a mere dialect difference that can
be completely rectified with a symbolic link, or an indication that my
docbook2X is misbuilt?
reply other threads:[~2009-03-12 12:24 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=5e68abd90903120522q635e41f9j118e74158ab04524@mail.gmail.com \
--to=tlholaday@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).