Re: Current CVS docs producing errors

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Rod Taylor <rbt(at)rbt(dot)ca>
Cc: PostgreSQL Docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Current CVS docs producing errors
Date: 2003-06-25 03:18:56
Message-ID: 20030625031856.GA3521@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Jun 24, 2003 at 22:52:32 -0400,
Rod Taylor <rbt(at)rbt(dot)ca> wrote:
> Seems you were caught in mid patch.
>
> They work with cvs sources from 30 minutes ago.
>
> Try updating and re-running -- the last error in particular was caused
> by 2 patches crossing in the night (patch queue).

I resynced and picked up a new perform.sgml and TODO.sgml. This got rid
of one of the errors. I am still seeing all of the datatype.sgml errors.
I wasn't getting these errors a couple of days ago.

>
> On Tue, 2003-06-24 at 22:52, Bruno Wolff III wrote:
> > When building postgres.tar.gz I get the following errors:
> >
> > make -C sgml clean
> > make[1]: Entering directory `/usr/local/src/postgresql-7.4/pgsql/doc/src/sgml'
> > rm -f HTML.manifest *.html *.gif
> > rm -rf *.1 *.l man1 manl manpage.refs manpage.links manpage.log
> > rm -f *.rtf *.tex-ps *.tex-pdf *.dvi *.aux *.log *.ps *.pdf *.out *.eps *.fot
> > rm -f HTML.index bookindex.sgml version.sgml features-supported.sgml features-unsupported.sgml
> > make[1]: Leaving directory `/usr/local/src/postgresql-7.4/pgsql/doc/src/sgml'
> > make -C sgml html
> > make[1]: Entering directory `/usr/local/src/postgresql-7.4/pgsql/doc/src/sgml'
> > /usr/bin/perl /usr/local/share/sgml/stylesheets/docbook/bin/collateindex.pl -f -g -o bookindex.sgml -N
> > { \
> > echo "<!entity version \"7.4devel\">"; \
> > echo "<!entity majorversion \"`expr 7.4devel : '\([0-9][0-9]*\.[0-9][0-9]*\)'`\">"; \
> > } >version.sgml
> > /usr/bin/perl ./mk_feature_tables.pl YES ../../../src/backend/catalog/sql_feature_packages.txt ../../../src/backend/catalog/sql_features.txt > features-supported.sgml
> > /usr/bin/perl ./mk_feature_tables.pl NO ../../../src/backend/catalog/sql_feature_packages.txt ../../../src/backend/catalog/sql_features.txt > features-unsupported.sgml
> > openjade -V draft-mode -D . -c /usr/local/share/sgml/stylesheets/docbook/catalog -d stylesheet.dsl -i output-html -t sgml postgres.sgml
> > openjade:datatype.sgml:2611:12:E: document type does not allow element "ROW" here
> > openjade:datatype.sgml:2616:12:E: document type does not allow element "ROW" here
> > openjade:datatype.sgml:2621:5:E: document type does not allow element "ROW" here
> > openjade:datatype.sgml:2625:5:E: document type does not allow element "ROW" here
> > openjade:datatype.sgml:2629:14:E: end tag for "ROW" omitted, but OMITTAG NO was specified
> > openjade:datatype.sgml:2625:1: start tag was here
> > openjade:datatype.sgml:2629:14:E: end tag for "ROW" omitted, but OMITTAG NO was specified
> > openjade:datatype.sgml:2621:1: start tag was here
> > openjade:datatype.sgml:2629:14:E: end tag for "ROW" omitted, but OMITTAG NO was specified
> > openjade:datatype.sgml:2607:1: start tag was here
> > openjade:perform.sgml:69:19:X: reference to non-existent ID "RUNTIME-CONFIG-OPTIMIZER"
> > openjade:/usr/local/share/sgml/stylesheets/docbook/html/../common/dbtable.dsl:224:13:E: 2nd argument for primitive "ancestor" of wrong type: "#<unknown object 145061872>" not a singleton node list
> > openjade:/usr/local/share/sgml/stylesheets/docbook/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'RUNTIME-CONFIG-OPTIMIZER'
> > make[1]: *** [html] Error 1
> > make[1]: Leaving directory `/usr/local/src/postgresql-7.4/pgsql/doc/src/sgml'
> > make: *** [postgres.tar] Error 2
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faqs/FAQ.html
> --
> Rod Taylor <rbt(at)rbt(dot)ca>
>
> PGP Key: http://www.rbt.ca/rbtpub.asc

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Rod Taylor 2003-06-25 03:20:52 Re: Current CVS docs producing errors
Previous Message Bruce Momjian 2003-06-25 02:59:26 Re: Current CVS docs producing errors