[MacPorts] #62354: docbook-utils-0.6.14 fails to build --

[MacPorts]

#62354: docbook-utils-0.6.14 fails to build --
----------------------------+----------------------
  Reporter:  jeremyhu       |      Owner:  lockhart
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:
Resolution:                 |   Keywords:
      Port:  docbook-utils  |
----------------------------+----------------------

Comment (by jeremyhu):

 The attached script is an updated version of the current script to install
 dependencies of the XQuartz build system.  I'm trying now to build and
 install documentation, but that's failing due to docbook-utils.  The
 installation line (from a fresh install of base) is:

 {{{
 $ sudo port -N -v install autoconf automake pkgconfig libtool py39-mako
 meson xmlto asciidoc doxygen fop groff docbook-utils
 }}}

 To try and reduce this to see if a conflict is causing it, I then did:

 {{{
 $ sudo port -v deactivate active
 $ sudo port -N -v -s install docbook-utils
 }}}

 and that worked.  Thus something in that small set of other project is
 causing a conflict.

 {{{
 $ sudo port -v uninstall docbook-utils
 $ sudo port -N -v install autoconf automake pkgconfig libtool
 $ sudo port -N -v -s install docbook-utils
 }}}

 That worked... uninstalled docbook-utils again and then:

 {{{
 $ sudo port -v uninstall docbook-utils
 $ sudo port -N -v -s install py39-mako meson xmlto asciidoc
 $ sudo port -N -v -s install docbook-utils
 }}}

 worked again... rince and repeat with the last set

 {{{
 $ sudo port -v uninstall docbook-utils
 $ sudo port -N -v -s install doxygen fop groff
 $ sudo port -N -v -s install docbook-utils
 }}}

 and that succeeded.

 I then decided to deactivate everyhitng and try re-installing en-mass, and
 that failed!

 Something odd is going on here.  The only real difference is that docbook-
 utils's dependencies were laid down after libtool in the working case and
 after groff in the failing case.  Given that we're using the same built
 archives, this means that something about the activation scripts is
 relevant here since the tarball content is the same in all cacses.

-- 
Ticket URL: <https://trac.macports.org/ticket/62354#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS