From: Michael J Gruber <git@drmicha•warpmail.net>
To: Drew Northup <drew.northup@maine•edu>
Cc: Francis Moreau <francis.moro@gmail•com>, git@vger•kernel.org
Subject: Re: Can't build doc anymore (v1.7.3.2)
Date: Tue, 23 Nov 2010 14:59:37 +0100 [thread overview]
Message-ID: <4CEBC8C9.4010905@drmicha.warpmail.net> (raw)
In-Reply-To: <1290517990.10366.17.camel@drew-northup.unet.maine.edu>
Drew Northup venit, vidit, dixit 23.11.2010 14:13:
>
> On Tue, 2010-11-23 at 09:45 +0100, Michael J Gruber wrote:
>> Francis Moreau venit, vidit, dixit 23.11.2010 08:50:
>>> Drew Northup <drew.northup@maine•edu> writes:
>>>
>>> [...]
>>>
>>>> Supposedly docbook-dtds-1.0-53.fc14 contains the files needed. I would
>>>> check to make sure that your /usr/share/sgml/docbook/xmlcatalog file is
>>>> correct. If it is it will contain a line an awful lot like the
>>>> following:
>>>> <public publicId="-//OASIS//DTD DocBook XML V4.5//EN" uri="xml-dtd-4.5/docbookx.dtd"/>
>>>
>>> It doesn't seem so:
>>>
>>> $ cat /usr/share/sgml/docbook/xmlcatalog
>>> <?xml version="1.0"?>
>>> <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
>>> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
>
> Ok, before we get too far down the rabbit hole, is that EVERYTHING in
> your xmlcatalog? If it is then you have an install error (I downloaded
> the spec file and read it extra closely just to be sure). In FC14 the
> xmlcatalog file is not provided as whole cloth but it is built by the
> post-install script. If that script failed to run to completion you will
> have missing parts to your docbook-dtds package installation.
>
>
>>> This file belongs to xml-common-0.6.3-33.fc14.noarch which sounds pretty
>>> uptodate for a Fedora distribution.
>
> Yes, it is the latest in the FC git repo collection for that package as
> well.
>
>>>
>>> Here's a list of some packages installed on my system that might be
>>> relevant:
>>>
>>> asciidoc-8.4.5-5.fc14.noarch
>>> docbook-utils-0.6.14-26.fc14.noarch
>>> docbook-style-xsl-1.75.2-6.fc14.noarch
>>> docbook-style-dsssl-1.79-11.fc14.noarch
>>> docbook-dtds-1.0-53.fc14.noarch
>>> xml-commons-resolver-1.2-4.fc14.noarch
>>> xmlto-0.0.23-3.fc13.x86_64
>>> xmltex-20020625-16.fc13.noarch
>>> libxml2-devel-2.7.7-2.fc14.x86_64
>>> libxml2-python-2.7.7-2.fc14.x86_64
>>> libxml++-2.30.1-1.fc14.x86_64
>>> libxml2-2.7.7-2.fc14.i686
>>> libxml++-2.30.1-1.fc14.i686
>>> xml-common-0.6.3-33.fc14.noarch
>>> xml-commons-apis-1.4.01-1.fc13.noarch
>>>
>>
>> I have no problems building the doc on F14 with
>>
>> ASCIIDOC8=y
>> ASCIIDOC_NO_ROFF=y
>> DOCBOOK2X_TEXI=db2x_docbook2texi
>>
>> in my config.mak (besides other stuff), with these versions:
>>
>> asciidoc-8.4.5-5.fc14.noarch
>> docbook2X-0.8.8-7.fc14.x86_64
>> docbook-dtds-1.0-53.fc14.noarch
>> docbook-style-dsssl-1.79-11.fc14.noarch
>> docbook-style-xsl-1.75.2-6.fc14.noarch
>> docbook-utils-0.6.14-26.fc14.noarch
>> libxml2-2.7.7-2.fc14.x86_64
>> libxml++-2.32.0-1.fc14.x86_64
>> libxml2-python-2.7.7-2.fc14.x86_64
>> python-lxml-2.2.8-1.fc14.x86_64
>> xml-common-0.6.3-33.fc14.noarch
>> xmlto-0.0.23-3.fc13.x86_64
>>
>> (libxml is irrelevant)
>>
>> Are you sure you have no other xmlto (type -a xmlto) and no tinkering
>> with the default style sheet config?
>>
>> Michael
>
> Before you get too much further along chasing phantoms, please have a
> look back into the mailing list at the problems I had just enumerated
> with respect to building the man pages when missing the docbook 4.5
> declarations and files in my local xmlcatalog. I got EXACTLY THE SAME
> ERRORS ORIGINALLY NOTED. That's why I answered the original query to the
> list.
>
> I recommend re-installing the docbook-dtds package alone and in
> isolation from other Yum/RPM transactions. If the xmlcatalog file is
> correctly regenerated AND the docbook files are there AND you have
> (re)run ./configure prior to running make AND you don't have filesystem
Don't do that unless you're using configure for git usually. I don't
think Francis is, he's setting make variables.
> errors THEN you should have a successful build. (Barring something that
> crawls up out of the rabbit hole--other than a rabbit.)
>
> Fix the most obvious possible problems first before seeking
> off-the-beaten-path solutions or worse blaming somebody.
>
???
catalog sent to Francis off-list, which closes this topic for me.
Michael
next prev parent reply other threads:[~2010-11-23 14:01 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
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 [this message]
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=4CEBC8C9.4010905@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=drew.northup@maine$(echo .)edu \
--cc=francis.moro@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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