docbook-utils: "..." is not a function name

[ryandesign (Ryan Carsten Schmidt)]

Building docbook-utils @0.6.14_1 fails for me. The log has lines like these:

:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:9:19:E: "X21B7" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:9:19:E: "X21B7" is not a function name
:info:build onsgmls:/opt/local/share/xml/docbook/4.1.2/ent/iso-amsa.ent:9:19:E: "X21B7" is not a function name
[snip]

And so on (7500 more lines like these).

[ryandesign (Ryan Carsten Schmidt)]

Deactivating docbook-xml-4.1.2 for the duration of the docbook-utils works.

[ryandesign (Ryan Carsten Schmidt)]

And now, after resolving #37131 (which was the reason I was trying to install docbook-utils at all), I can't reproduce the problem—even if I revert the change I made to fix that ticket. I don't really understand why. Maybe my docbook xml catalog just needed to rebuilt—which happened when I deactivated/reactivated docbook-xml-4.1.2.

[lockhart (Thomas Lockhart)]

Replying to ryandesign@…:

And now, after resolving #37131 (which was the reason I was trying to install docbook-utils at all), I can't reproduce the problem—even if I revert the change I made to fix that ticket. I don't really understand why. Maybe my docbook xml catalog just needed to rebuilt—which happened when I deactivated/reactivated docbook-xml-4.1.2.

The problem is with the package textproc/iso8879, which needs to have been installed before the docbook-sgml-4.2 package so that the catalog entry for iso8879 appears before the specific docbook entries in the global catalog file /opt/local/etc/sgml/catalog. I think a from-scratch installation may get things in the right order, but I've noticed problems when installing and de-installing packages. I'm working on restructuring the docbook and related packages to try to guarantee order and to consolidate common code (there were almost a dozen packages trying to create that global catalog if it did not exist), and pixilla has been helpful in giving advice on the approach to take.

[davidfavor (David Favor)]

Fresh install of docbook-utils throws same error for me.

[cooljeanius (Eric Gallager)]

Cc Me!

[cooljeanius (Eric Gallager)]

Replying to lockhart@…:

Replying to ryandesign@…:

And now, after resolving #37131 (which was the reason I was trying to install docbook-utils at all), I can't reproduce the problem—even if I revert the change I made to fix that ticket. I don't really understand why. Maybe my docbook xml catalog just needed to rebuilt—which happened when I deactivated/reactivated docbook-xml-4.1.2.

The problem is with the package textproc/iso8879, which needs to have been installed before the docbook-sgml-4.2 package so that the catalog entry for iso8879 appears before the specific docbook entries in the global catalog file /opt/local/etc/sgml/catalog. I think a from-scratch installation may get things in the right order, but I've noticed problems when installing and de-installing packages.

docbook-sgml-4.2 currently lists iso8879 as a runtime dependency, does the buildbot install those? If not then it should probably be listed as a build dependency as well.

Edit: actually I still get this issue even after installing the above in the correct order, so maybe it is something else?

Double edit: deactivating docbook-xml-4.1.2 allowed it to build successfully, so maybe the conflicts_build 1.0 PortGroup could be used to add a conflicts_build on docbook-xml-4.1.2?

[lockhart (Thomas Lockhart)]

This should be resolved by recent consolidation of xml and sgml catalog support around the xmlcatalog portgroup.

[pixilla (Bradley Giesbrecht)]

Newer patches should have addressed the symptom.

[jeremyhu (Jeremy Huddleston Sequoia)]

I don't think this was ever fixed. I remember this being a problem the last time I tried to build documentation for XQuartz 5 years ago, and it's biting me again now. #62354.

[Lisias (Lisias)]

Replying to jeremyhu:

I don't think this was ever fixed. I remember this being a problem the last time I tried to build documentation for XQuartz 5 years ago, and it's biting me again now. #62354.

This problem had bitten me in the… back… today. Looking for it, I found a fix!!!

sudo port uninstall docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 iso8879 docbook-xml-4.2 openjade docbook-sgml-4.2 docbook-utils p5.22-sgmlspm docbook-dsssl docbook-xml-5.0 docbook-xsl docbook-xsl-ns sgml-common
sudo rm -rf /opt/local/etc/sgml /opt/local/etc/xml
sudo port install -s docbook-utils

source: ticket:48297#comment:4