At the end of each self-update I get the following error message, in spite of whether I respond with yes or no:
++++++++++++++++++++++++++++++++++++++++ ---> Updating database of binaries ---> Scanning binaries for linking errors Could not open /opt/local/lib/libgstgl-1.0.0.dylib: Error opening or reading file (referenced from /opt/local/lib/libwebkit2gtk-4.0.37.44.4.dylib) ---> Found 6 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 ++++++++++++++++++++++++++++++++++++++++ I get the following warning: sudo port diagnose Password: Warning: found dylibs in your /usr/local/lib directory. These are known to cause problems. We'd recommend you remove them. Warning: found header files in your /usr/local/include directory. These are known to cause problems. We'd recommend you remove them. ls /usr/local/lib cmake docker libgmp.a libgmp.la libprimesieve.a perl5 pkgconfig sudo /bin/rm /usr/local/lib/libgmp.a sudo /bin/rm /usr/local/lib/libgmp.la sudo /bin/rm /usr/local/lib/libprimesieve.a ls /usr/local/include pari primesieve primesieve.hpp sudo /bin/rm /usr/local/include/primesieve.hpp sudo port diagnose [no output!] Now when doing self-update when there's nothing new in ports I get this: port outdated The following installed ports are outdated: borgbackup 1.2.7_1 < 1.2.8_1 mpv 0.37.0_2 < 0.37.0_3 octave 8.4.0_2 < 9.1.0_0 This is a different issue which I will discuss in a different email. Now when I have an upgrade or install will I still have a broken link error message at the end of the port upgrade or install process? I have a build log (attached, since it is very small). Thanks, Ken Wolcott
build_failed_webkit2-gtk.log
Description: Binary data
