id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,port 33847,"clang-2.9, clang-3.0, clang3.1: /opt/local/libexec/llvm-*/bin/ld already exists and does not belong to a registered port",ryandesign,jeremyhu,"The [http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/6021/steps/compile/logs/stdio buildbot reports] that clang-2.9, clang-3.0 and clang-3.1 fail activation because of the presence of unregistered files /opt/local/libexec/llvm-*/bin/ld: clang-2.9: `Error: Target org.macports.activate returned: Image error: /opt/local/libexec/llvm-2.9/bin/ld already exists and does not belong to a registered port. Unable to activate port clang-2.9. Use 'port -f activate clang-2.9' to force the activation.` clang-3.0: `Error: Target org.macports.activate returned: Image error: /opt/local/libexec/llvm-3.0/bin/ld already exists and does not belong to a registered port. Unable to activate port clang-3.0. Use 'port -f activate clang-3.0' to force the activation.` clang-3.1: `Error: Target org.macports.activate returned: Image error: /opt/local/libexec/llvm-3.1/bin/ld already exists and does not belong to a registered port. Unable to activate port clang-3.1. Use 'port -f activate clang-3.1' to force the activation.` I have {clang,llvm}-{2.9,3.0} installed on my system (not yet updated to the very latest version), and /opt/local/libexec/llvm-*/bin/ld does not exist on my system. Not sure what caused these files to get installed on the buildbot but not on my system. But it sounds like maybe an older version of the ports inadvertently installed these files directly into ${prefix} bypassing ${destroot}. It would probably be best for the clang ports need to clean up this situation. See the bottom of r38613 for an example of how this can be done.",defect,closed,Normal,,ports,2.0.4,fixed,,,"clang-2.9, clang-3.0, clang-3.1"