From: Francis Moreau <francis.moro@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Drew Northup <drew.northup@maine.edu>, git@vger.kernel.org
Subject: Re: Can't build doc anymore (v1.7.3.2)
Date: Tue, 23 Nov 2010 10:32:01 +0100 [thread overview]
Message-ID: <m2zkt0jsha.fsf@gmail.com> (raw)
In-Reply-To: <4CEB8774.7050504@drmicha.warpmail.net> (Michael J. Gruber's message of "Tue, 23 Nov 2010 10:20:52 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
[...]
>
> That's what they all say ;)
>
But they were all drunk ;)
>
> How successful is:
>
> make XMLTO_EXTRA="--skip-validation" doc
>
still failing:
$ make prefix=/usr/local NO_CURL=1 ASCIIDOC8=y DOCBOOK2X_TEXI=db2x_docbook2texi ASCIIDOC_NO_ROFF=y XMLTO_EXTRA="--skip-validation" V=1 doc
make -C Documentation all
make[1]: Entering directory `/home/fmoreau/git/Documentation'
make -C ../ GIT-VERSION-FILE
make[2]: Entering directory `/home/fmoreau/git'
make[2]: `GIT-VERSION-FILE' is up to date.
make[2]: Leaving directory `/home/fmoreau/git'
rm -f git-fetch.1 && \
xmlto -m manpage-normal.xsl --skip-validation man git-fetch.xml
I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"
compilation error: file /tmp/xmlto-xsl.A7kzn5 line 4 element import
xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
make[1]: *** [git-fetch.1] Error 1
make[1]: Leaving directory `/home/fmoreau/git/Documentation'
make: *** [doc] Error 2
> This should avoid hitting the network for the dtd under all
> circumstances. (Are you online when make'ing?)
Yes I am.
> Normally, the catalogue should take care of that but this seems to be
> failing for you.
>
> Just to make sure: You're not building as root, are you?
>
No, I'm not building as root.
> You can also use the quick-install-doc target, of course, but we want
> install-doc to work as well on a mainstream distro.
Yes I know but I wanted to report just in case there's something wrong
in the git doc build process.
Thanks
--
Francis
next prev parent reply other threads:[~2010-11-23 9:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 19:45 Can't build doc anymore (v1.7.3.2) Francis Moreau
2010-11-22 20:35 ` Drew Northup
2010-11-22 20:44 ` Francis Moreau
2010-11-22 21:24 ` Drew Northup
2010-11-23 7:50 ` Francis Moreau
2010-11-23 8:45 ` Michael J Gruber
2010-11-23 9:05 ` Francis Moreau
2010-11-23 9:20 ` Michael J Gruber
2010-11-23 9:32 ` Francis Moreau [this message]
2010-11-23 10:01 ` Michael J Gruber
2010-11-23 11:24 ` Francis Moreau
2010-11-23 11:41 ` Michael J Gruber
2010-11-23 11:57 ` Francis Moreau
2010-11-23 12:04 ` Michael J Gruber
2010-11-23 12:31 ` Francis Moreau
2010-11-23 13:13 ` Drew Northup
2010-11-23 13:59 ` Michael J Gruber
2010-11-23 16:36 ` Francis Moreau
2010-11-23 17:06 ` Drew Northup
2010-11-23 20:48 ` Francis Moreau
2010-11-24 19:17 ` Junio C Hamano
2010-11-25 8:13 ` git
2010-11-25 19:54 ` Francis Moreau
2010-11-23 16:30 ` Francis Moreau
2010-11-22 21:01 ` Pascal Obry
2010-11-22 21:14 ` Francis Moreau
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=m2zkt0jsha.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@drmicha.warpmail.net \
--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).