Created attachment 184880 [details]
Reports such errors which often lead to later crashes.
One caveat that I know of is when executable is linked to the shared library by its absolute path. Such library isn't normally found by ldd in a stage directory until installed. Maybe somebody can suggest a solution to this. In case of relative shared library links, and in case of inter-package links it should work fine.
* I artificially linked one executable to both SSLs and got this error:
> Error: /usr/local/bin/qtox is linked to /usr/local/lib/libssl.so.9 from security/openssl but it is not declared as a dependency
Open to suggestions.
Correction, the error message is:
> Error: /usr/local/bin/qtox is linked to both base and port SSL libraries: /usr/lib/libssl.so.8 /lib/libcrypto.so.8 and /usr/local/lib/libssl.so.9 /usr/local/lib/libcrypto.so.9
Created attachment 184881 [details]
Created attachment 184882 [details]
It needs to be generalized to include the mix of libgcc_s.so from the base and from gfortran.
Created attachment 184925 [details]
Added libgcc_s check.
It might fail for many ports including fortran parts because many of them are broken.
Created attachment 184926 [details]
Could you create a review on phabricator ? it feels like the we're back in the stone age trying to review this here.
For the record, /lib/libedit.so.7 can also conflict with the port's version /usr/local/lib/libedit.so.0. This pair needs to be added to the check.