Multiple ports error on upgrade

Ryan Schmidt ryandesign at
Tue Mar 8 16:56:15 PST 2011

On Mar 8, 2011, at 10:06, Philip Hudson wrote:

> On 3 Mar, 2011, at 3:30 pm, Ryan Schmidt wrote:
>> 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")

> Thanks for that. Did a sudo port clean --all all, then upgrade produced the following again:

>> :info:build dso_dlfcn.c:84:20: error: dlfcn.h: No such file or directory

dlfcn.h ought to exist in /usr/include/dlfcn.h. Does it? If not, your OS is incomplete and this file and any others that are missing will have to be restored from your backups or reinstalled from your Mac OS X DVD. If it does exist, then I'm not sure why it can't be found; we may need to see the complete main.log file to be able to diagnose this further.

More information about the macports-users mailing list