[MacPorts] #39572: harfbuzz error

[MacPorts]

#39572: harfbuzz error
---------------------------+--------------------------
  Reporter:  pleburan45@…  |      Owner:  ryandesign@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.3
Resolution:                |   Keywords:
      Port:  harfbuzz      |
---------------------------+--------------------------

Comment (by ryandesign@…):

 That looks normal, except: did you run "icu-config- --version" as you
 showed above, or "icu-config --version" as I asked? The program should be
 called "icu-config" not "icu-config-" but your main.log file shows icu-
 config could not be found. If the program has somehow been renamed to have
 a dash at the end of its name, that would explain the problem, though that
 would be a strange thing to have happen. It would help if you attach the
 file
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_harfbuzz/harfbuzz/work/harfbuzz-0.9.18/config.log
 which might contain more details about how harfbuzz tried (and failed) to
 find icu.

 There were a couple related problems. icu is optional for harfbuzz, so
 when it couldn't find your icu, it continued to try to build without icu
 support. I never intended for that to happen in MacPorts; I intended icu
 support to be always-on. Also there was a bug in the harfbuzz build system
 that made it fail when icu was not used. They've fixed it but haven't
 released a new version yet. I applied the patch to the port. Also I've
 separated icu support into its own harfbuzz-icu port, as the developers of
 harfbuzz now recommend. These changes are in r107441. This means if you
 "sudo port selfupdate" and try again to install harfbuzz, it should now
 succeed, since icu is no longer needed. However, there still seems to be
 something wrong with your icu installation. If you try to install the new
 harfbuzz-icu port, it should fail, as might other ports that need icu, so
 it would be good to solve that mystery by examining the config.log.

-- 
Ticket URL: <https://trac.macports.org/ticket/39572#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X