Multiple ports error on upgrade

Ryan Schmidt ryandesign at
Thu Mar 3 07:30:07 PST 2011

On Mar 3, 2011, at 09:20, Philip Hudson wrote:

> On 2 Mar, 2011, at 4:02 pm, Ryan Schmidt wrote:
>> Sounds like you have a rogue dlfcn.h header, either in /usr/local/include or /opt/local/include, which should be removed. If it's in /usr/local, remove it, and anything else you may have in /usr/local; having things in /usr/local is a great way to cause problems for MacPorts. If it's in /opt/local, use "port provides" to find out what port provided it; if it's not provided by a port, remove it; if it is, let us know what port so we can investigate.
> I did indeed have a file /usr/local/include/dlfcn.h; I deleted it, re-ran port upgrade, and got exactly the same error and log.

Clean the affected port and try again. ("sudo port clean")

> sudo find /opt -name dlfcn.h reveals 4 files (3 distinct according to diff) under /opt/local/var/macports/build, two each for xulrunner and Python 2.7.1. Each is "not provided by a MacPorts port" according to port provides.

Correct, things in /opt/local/var/macports/ aren't registered to ports; that's ok and not a problem, and having dlfcn.h or other files there is not a problem. It's only a problem if the file is in a path that's searched for include files. Those paths are at least /usr/include, /usr/local/include, /opt/local/include.

More information about the macports-users mailing list