[MacPorts] #71891: pango @1.55.0 does not build on PPC Mac OS X 10.4.11, Tiger, because of help2man: can't get `--help-all' info from /opt/local/var/macports/build/nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/build/utils/pango-view

[MacPorts]

#71891: pango @1.55.0 does not build on PPC Mac OS X 10.4.11, Tiger, because of
help2man: can't get `--help-all' info from
/opt/local/var/macports/build/nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/build/utils
/pango-view
------------------------+-----------------------
  Reporter:  ballapete  |      Owner:  (none)
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.10.5
Resolution:  duplicate  |   Keywords:  tiger ppc
      Port:  pango      |
------------------------+-----------------------
Changes (by ryandesign):

 * cc: ryandesign@…, mascguy@… (removed)
 * cc: ryandesign, mascguy (added)
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Replying to [ticket:71891 ballapete]:
 > {{{
 > help2man: can't get `--help-all' info from
 /opt/local/var/macports/build/nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/build/utils
 /pango-view
 > Try `--no-discard-stderr' if option outputs to stderr
 > }}}

 Duplicate of #69876.

 Replying to [comment:1 ballapete]:
 > {{{
 > dyld: Library not loaded: /opt/local/lib/libicuuc.74.dylib
 >   Referenced from: /opt/local/lib/libxml2.2.dylib
 >   Reason: image not found
 > }}}

 Upgrade libxml2 so that it links with the new libicuuc. This should have
 happened automatically since libxml2 is a dependency of pango, eventually,
 but MacPorts can't upgrade dependencies properly if a dependency cycle
 exists, so perhaps one exists on your platform.

 Replying to [comment:2 ballapete]:
 > Has `help2man`'s failure the same cause as `convert`'s failure in `p5.34
 -pdf-builder`, #71473?

 I have not attempted to read that ticket today.

 Replying to [comment:3 ballapete]:
 > The reason is that `port` did not observe that some `port`s need to be
 rebuilt:
 >
 > {{{
 > The following ports will be rebuilt:
 >  boost176 @1.76.0+no_single+no_static+python312
 >  boost178 @1.78.0+no_single+no_static+python312
 >  libxml2 @2.13.5
 >  harfbuzz-icu @10.1.0
 >  texlive-bin @2024.70613+x11
 > Continue? [Y/n]: DEBUG: epoch: in tree: 0 installed: 0
 > }}}

 Possibly due to a dependency cycle. You or someone would need to identify
 what the cycle is and how to break it.

 > Is the `rev-upgrade` check only run after a little success? Then this is
 the wrong path, because it produces fake success.

 rev-upgrade is run after install and upgrade. There are definitely ways
 for ports to break at times other than install and upgrade.

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