[MacPorts] #66748: fpm fails to build on Tiger: dyld: Library not loaded: /opt/local/lib/libunistring.2.dylib

[MacPorts]

#66748: fpm fails to build on Tiger: dyld: Library not loaded:
/opt/local/lib/libunistring.2.dylib
---------------------------+----------------------------
  Reporter:  barracuda156  |      Owner:  barracuda156
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.8.0
Resolution:                |   Keywords:  powerpc, tiger
      Port:  fpm           |
---------------------------+----------------------------

Comment (by ryandesign):

 This isn't an fpm bug. It seems to be a problem specific to your computer.

 fpm's install.sh uses curl to download files. curl is linked with
 libpsl—currently libpsl.5.dylib. libpsl is linked with libunistring—on
 your machine, libunistring.2.dylib, but that doesn't exist anymore;
 libunistring.5.dylib exists now. libpsl needs to be rebuilt now that
 libunistring has been updated.

 libunistring was last updated (to 1.1_0)
 [changeset:477767404eb285d781efab316e409966a3c92bb3/macports-ports on
 October 22, 2022]. It's presumably at that time that its dylib version
 changed to 5, therefore all ports that link with libunistring had their
 revisions increased (e.g. libpsl was updated from 0.21.1_0 to 0.21.1_1)
 [changeset:23e19bdf5449fcdb11089a2fd938fb5322f3e541/macports-ports the
 same day]. That should have taken care of the problem, assuming that
 sometime after October 22, 2022 you've run:
 {{{
 sudo port selfupdate
 sudo port upgrade outdated
 }}}

 If you've already done that and you already have libpsl @0.21.1_1 or later
 installed and active, then it was evidently built erroneously against the
 old libunistring. The solution would be to rebuild it against the current
 libunistring:
 {{{
 sudo port -n upgrade --force libpsl
 }}}

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