[MacPorts] ProblemHotlist modified

[MacPorts]

Changed page "ProblemHotlist" by ryandesign at macports.org from 70.253.69.7*
Page URL: <https://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <https://trac.macports.org/wiki/ProblemHotlist?action=diff&version=65>
Revision 65

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 64)
+++ ProblemHotlist (version: 65)
@@ -50,7 +50,13 @@
 {{{
 Error: Target org.macports.activate returned: Image error: /opt/local/bin/xmlwf already exists and does not belong to a registered port.  Unable to activate port expat.
 }}}
-xmlwf is a part of the expat port (which is a dependency of many other ports, and thus is likely to be one of the first ports to ever get installed), but for some reason this file already exists on your computer, and MacPorts did not install it. The reason is that you have installed a 3rd-party software package -- possibly [http://www.swi-prolog.org/ swi-prolog] -- which was itself built with MacPorts, set to its default prefix, and therefore conflicts with your normal use of MacPorts in its default prefix. The developers of the 3rd-party package you installed should not have distributed their software in this manner; they should have configured MacPorts in a custom prefix instead, one that is unique to their software. (For example, in the case of swi-prolog, /usr/local/swi-prolog or /opt/swi-prolog would be good choices.) The cleanest solution for you at this point is to follow the [http://guide.macports.org/chunked/installing.macports.uninstalling.html MacPorts uninstallation instructions]. This will also remove the 3rd-party software package that installed itself unannounced into MacPorts' prefix. Then you can [http://guide.macports.org/chunked/installing.macports.html install MacPorts] again.
+xmlwf is a part of the expat port (which is a dependency of many other ports, and thus is likely to be one of the first ports to ever get installed), but for some reason this file already exists on your computer, and MacPorts did not install it.
+
+One reason for this is that you have installed a 3rd-party software package -- possibly [http://www.swi-prolog.org/ swi-prolog] -- which was itself built with MacPorts, set to its default prefix, and therefore conflicts with your normal use of MacPorts in its default prefix. The developers of the 3rd-party package you installed should not have distributed their software in this manner; they should have configured MacPorts in a custom prefix instead, one that is unique to their software. (For example, in the case of swi-prolog, /usr/local/swi-prolog or /opt/swi-prolog would be good choices.)
+
+Another reason is that you previously had MacPorts (and expat and probably other ports) installed, then somehow uninstalled MacPorts itself, or at least its registry of which ports are installed, without actually uninstalling those ports, and have now installed MacPorts again with a clean registry, which therefore thinks no ports are installed, though some still are.
+
+Either way, the cleanest solution for you at this point is to follow the [http://guide.macports.org/chunked/installing.macports.uninstalling.html MacPorts uninstallation instructions]. This will also remove the 3rd-party software package that installed itself unannounced into MacPorts' prefix. Then you can [http://guide.macports.org/chunked/installing.macports.html install MacPorts] again.
 
 == A command failed to run with a message referring to libpng12.0.dylib == #libpng
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on ProblemHotlist. If it was not you, please
report to .