"port upgrade" error message usability

[Julien Salort]

Le 30/01/2022 à 10:30, Andrew Janke a écrit :

> I'm the primary maintainer for Octave.app (https://octave-app.org/), a 
> "native Mac app" distribution of GNU Octave 
> (https://www.gnu.org/software/octave/index), and I'm getting more in 
> to MacPorts recently because Octave.app is currently built on Homebrew 
> and I'm considering migrating it to MacPorts, because I want to 
> continue supporting macOS 10.14 with it. (10.15+ breaks some apps, so 
> I want to be able to support the diehards (like me) who are sticking 
> with 10.14).) 

That's very interesting. Maybe you will be able to help fix the Octave port.

I haven't been able to install it on Monterey. It seems to be a linking 
problem, but the Octave Portfile is too complex for me to try and fix 
it. There are open tickets for this issue, which have been opened for 
nearly a year:

https://trac.macports.org/ticket/62874

also for arm64:

https://trac.macports.org/ticket/61860

The log says:

:info:destroot dyld[24113]: Library not loaded: @rpath/libgfortran.5.dylib
:info:destroot   Referenced from: 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/octave-6.4.0/src/.libs/octave-cli
:info:destroot   Reason: tried: 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/octave-6.4.0/libinterp/.libs/libgfortran.5.dylib' 
(no such file), 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/octave-6.4.0/liboctave/.libs/libgfortran.5.dylib' 
(no such file), '/usr/local/lib/libgfortran.5.dylib' (no such file), 
'/usr/lib/libgfortran.5.dylib' (no such file)
:info:destroot Command failed: ./run-octave -cli -q -f -H --eval 'try; 
pkg prefix 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/destroot/opt/local/share/octave/packages 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/destroot/opt/local/lib/octave/packages; 
pkg global_list 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_octave/octave/work/destroot/opt/local/share/octave/octave_packages; 
pkg -verbose -global rebuild; disp(lasterror.message); catch; exit(1); 
end_try_catch;'

Someone proposed a workaround by manually changing to the actual path, 
and it seems to work. If someone could explain clearly what this @rpath 
thing actually is, and if there is a way to fix it globally, I would be 
interested to know.

Julien