Cleaning up Perl mess

Jeremy Lavergne jeremy at
Fri Nov 16 11:59:27 PST 2012

> I cut the sentence short here and makes no sense. What I meant to say
> is that it would seem that some binaries depend on dylibs that are
> actually part of Perl modules and that seems really weird. I have no
> way of finding out exactly which binaries were depending on these
> dylibs.
> Example:
> /opt/local/lib/perl5/site_perl/5.12.3/darwin-multi-2level/auto/Net/Libproxy/Libproxy.dylib:
> I don't think the message "Scanning binaries for linking errors: 7.9%"
> is accurate. I mean I don't think that it's complaining about these
> missing files because it's failing some otool -L test but rather
> because it's looking up in some port's database and finding that these
> files are missing. If it would tell me exactly which one I could try
> to fix it so that is what I'm asking: Is there a way to increase the
> verbosity or something that would tell me exactly what binaries it's
> referring to ???

Using -d (debug) outputs more verbosely than just -v (verbose) which is more than nothing at all which is more than -q (quiet). You can rerun `sudo port -d rev-upgrade` to see more output.

If the missing files are coming from port's database, then you should be able to ask what installed the file:
port provides /opt/local/lib/perl5/site_perl/5.12.3/darwin-multi-2level/auto/Net/Libproxy/Libproxy.dylib

More information about the macports-users mailing list