Opened 15 months ago

Last modified 15 months ago

#66748 assigned defect

fpm fails to build on Tiger: dyld: Library not loaded: /opt/local/lib/libunistring.2.dylib

Reported by: barracuda156 Owned by: barracuda156
Priority: Normal Milestone:
Component: ports Version: 2.8.0
Keywords: powerpc, tiger Cc:
Port: fpm

Description

--->  Building fpm
Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.7.0" && FPM_CFLAGS="-Os -arch ppc" FPM_LDFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.7.0/install.sh 
dyld: Library not loaded: /opt/local/lib/libunistring.2.dylib
  Referenced from: /opt/local/lib/libpsl.5.dylib
  Reason: image not found
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.7.0/install.sh: line 65:  5607 Trace/BPT trap          $FETCH $SOURCE_URL >$BOOTSTRAP_DIR/fpm.F90
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.7.0" && FPM_CFLAGS="-Os -arch ppc" FPM_LDFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_fpm/fpm/work/fpm-0.7.0/install.sh

Change History (2)

comment:1 Changed 15 months ago by ryandesign (Ryan Carsten Schmidt)

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) 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) 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

comment:2 in reply to:  1 Changed 15 months ago by barracuda156

Replying to 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) 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) 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

Thank you! Indeed, I upgraded few ports on 10.4 but not all. I will go through updates, it should be good then.

Note: See TracTickets for help on using tickets.