public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Wagner <andreasbwagner@gmail.com>
To: docbook-tools-discuss@sourceware.org
Subject: building docbook-utils for ArchLinux
Date: Wed, 05 May 2010 00:34:00 -0000	[thread overview]
Message-ID: <v2n58d839f51005041734iabf5f2b8s1652719820c386d7@mail.gmail.com> (raw)

Hello,

I am trying to get the docbook-utils PKGBUILD working for the Arch
User Repository.

I am starting with the PKGBUILDs here:
http://bbs.archlinux.org/viewtopic.php?id=29146

The full list of errors are on that page. Here's the part most likely
indicating the cause of the rest:

make[2]: Entering directory
`/home/suat/Abs/Lapis/denemeler/docbook-sgml-utils/src/docbook-utils-0.6.14/doc/HTML'
SGML_CATALOG_FILES=/etc/sgml/catalog
        SGML_SEARCH_PATH=../..:../../doc:..
                jade -t sgml -i html -d ../../docbook-utils.dsl#html
                        -V '%use-id-as-filename%' ../../doc/docbook-utils.sgml
jade:../../doc/docbook-utils.sgml:1:55:W: cannot generate system
identifier for public text "-//OASIS//DTD DocBook V3.1//EN"
jade:../../doc/docbook-utils.sgml:9:0:E: reference to entity "BOOK"
for which no system identifier could be generated
jade:../../doc/docbook-utils.sgml:1:0: entity was defined here

I think this is due to using the older doctype. I think this would be
fixed by installing doctype sgml dtd 3.1, but I would rather not add a
legacy package to the Arch repository just for this. Am I correct
about the error? If so will this be updated docbook-utils.sgml be
updated to the newer version soon?

Thanks,
Andreas

             reply	other threads:[~2010-05-05  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  0:34 Andreas Wagner [this message]
2010-05-08  8:37 ` Eric Bischoff

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=v2n58d839f51005041734iabf5f2b8s1652719820c386d7@mail.gmail.com \
    --to=andreasbwagner@gmail.com \
    --cc=docbook-tools-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).