[MacPorts] #62797: legacy-support @1.0.0_0 dyld: Library not loaded: @executable_path/../lib/libMacportsLegacySupport.dylib Reason: image not found

[MacPorts]

#62797: legacy-support @1.0.0_0 dyld: Library not loaded:
@executable_path/../lib/libMacportsLegacySupport.dylib Reason: image not
found
-----------------------------+--------------------
  Reporter:  cave-canem      |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.6.99
Resolution:                  |   Keywords:
      Port:  legacy-support  |
-----------------------------+--------------------

Comment (by kencu):

 hmm. Looks like the library is being buildt with the @executable_path
 embedded in it for testing as expected:

 https://github.com/macports/macports-legacy-
 support/blob/9e9e6bf62bb6e835eff9a9c1aca6ddde1bd09a40/Makefile#L40

 and there is an install phase that is supposed to rewrite that
 @executable_path to a full path here:

 https://github.com/macports/macports-legacy-
 support/blob/9e9e6bf62bb6e835eff9a9c1aca6ddde1bd09a40/Makefile#L316

 but -- it appears to be not changing the reference to
 libMacportsLegacySupport.dylib in libMacportsLegacySystem.B.dylib.

 We probably need one more install_name_tool step in the Makefile, but I
 will have to build it myself to see if that is so.

 The command should look something like this (for your prefix, untested so
 far):

 {{{
 sudo install_name_tool -change
 @executable_path/../lib/libMacportsLegacySupport.dylib
 /opt/MacPorts/lib/libMacportsLegacySupport.dylib
 /opt/MacPorts/lib/libMacportsLegacySystem.B.dylib
 }}}

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