[MacPorts] ProblemHotlist modified

Sun Jul 26 15:47:31 PDT 2009

Changed page "ProblemHotlist" by raimue at macports.org from 91.11.205.137*
Page URL: <http://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <http://trac.macports.org/wiki/ProblemHotlist?action=diff&version=45>
Revision 45
Comment: More consistent formatting

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================

--- ProblemHotlist (version: 44)
+++ ProblemHotlist (version: 45)
@@ -2,30 +2,41 @@
 
 (Note, if you're using Mac OS X 10.5.x, be sure also to check the LeopardProblems page)
 
-== man port fails with error message ==
-If you get following error message, when trying to access the man page for port or installed ports.
+== man port fails with error message == #manpath
+
+'''Error message:'''[[BR]]
 {{{
+$ man port
 Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>")
 No manual entry for port
 }}}
+
+'''Workaround:'''[[BR]]
+
 Add the following line to your .profile or .bash_profile.
 {{{
 unset MANPATH
 }}}
-Tracked in ticket #13444.
+
+'''Ticket:''' #13444[[BR]]
 
 == port fails with: Image error: /opt/local/bin/a2p... == #perl5-image-error
-The perl ports are currently in flux, and can potentially cause issues resulting in the error message
+
+'''Error message:'''[[BR]]
 {{{
 Error: Activating perl5 5.8.8_0 failed: Image error: /opt/local/bin/a2p is being used by the active perl5.8 port.  Please deactivate this port first, or use the -f flag to force the activation.
 }}}
+
+The perl ports recently changed the paths for builtin modules, which can potentially cause issues resulting in this error message.
+
+'''Workaround:'''[[BR]]
 The current method to get around this issue is to run
 {{{
 port -f uninstall perl5
 }}}
 then run your initial install command.
 
-== Fetch failures ==
+== Fetch failures == #fetch-failures
 
 If fetch failed for a port, you can still get the distfile from anywhere else. Maybe the homepage of the software lists alternative download locations for source tarballs. Just download the distfile and save it to `${prefix}/var/macports/distfiles/<portname>/`. Make sure you get a file with exactly the same name (watch out for `.tar.gz` and `.tar.bz2`!) If a `port clean --all` has been done the distfile directory will have been removed. The directory for each port is created at the beginning of the fetch phase.
 
@@ -72,14 +83,17 @@
 '''Known affected ports:''' taglib-devel[[BR]]
 '''Ticket:''' #18583[[BR]]
 
-== A port failed to build, upgrade, or run with a message referring to libintl.3.dylib ==
+== A port failed to build, upgrade, or run with a message referring to libintl.3.dylib == #libintl
 
+'''Error message:'''[[BR]]
 {{{
 dyld: Library not loaded: /opt/local/lib/libintl.3.dylib
 }}}
 
+'''Explanation:'''[[BR]]
 When the gettext port was updated from 0.14.x to 0.15.x, the libintl library version changed from 3 to 8. Software always links against a specific library version, so the ports you currently have installed that depend on gettext are linked to the now-nonexistent version 3 libintl library. To fix this problem, all ports that depend on gettext will need to be rebuilt so that they link with the new version 8 libintl library. This may be quite a few ports.
 
+'''Workaround:'''[[BR]]
 Here is a script that can tell you what ports you have installed that depend on gettext.
 
 {{{
@@ -122,13 +136,15 @@
 port -duf uninstall
 }}}
 
-== A port failed to build with a message referring to 1/lib: No such file or directory ==
+== A port failed to build with a message referring to 1/lib: No such file or directory == #lib-spaces
 
+'''Error message:'''[[BR]]
 {{{
 apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory
 make: *** Error 1
 }}}
 
+'''Explanation:'''[[BR]]
 When upgrading from Tiger to Leopard without removing the previous Mac OS version, updated versions of some libraries in {{{/usr/}}} and {{{/usr/lib/}}} are moved from {{{/old/path/}}} to {{{/old/path 1/}}}. Notice the space before {{{1}}}. This makes some {{{configure}}} scripts build bad build instructions, making the build phases of several ports fail.
 
 Two incriminated directories have been encountered :
@@ -137,6 +153,8 @@
 /usr/X11R6 1/
 /usr/lib/ruby 1/
 }}}
+
+'''Workaround:'''[[BR]]
 
 In order to fix this problem, you can remove the backups created by the installers, and then clean the work directory of the failed port so that its configure script will be re-run:
 {{{
@@ -154,15 +172,23 @@
 Running {{{sudo port uninstall libpng}}} or {{{sudo port uninstall libpng @1.2.30_0}}} will complain that other ports depend on libpng and you can't uninstall.  Simply add a -f to get it to go: {{{sudo port -f uninstall libpng @1.2.30_0}}}.  Just make sure you remove the older, inactive version.
 
 == Can't install python modules because of unrecognized --no-user-cfg == #no-user-cfg
-While trying to install python modules, if it fails with the message
+
+'''Error message:'''[[BR]]
 {{{
 error: option --no-user-cfg not recognized
 }}}
-your python port is outdated.  For py25-* modules, you need to upgrade python25, for py26-*, python26, and for py30-*, python30.
+
+'''Workaround:'''[[BR]]
+While trying to install python modules, if it fails with this message because your python port is outdated.  For py25-* modules, you need to upgrade python25, for py26-*, python26, and for py30-*, python30.
 
 == A port fails to build due to XPROTO == #xproto
+
+'''Error message:'''[[BR]]
 When building a port which depends on some X11-based ports, it fails with
 {{{
-Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11
+Requested 'xproto >= 7.0.XY' but version of Xproto is 7.0.11
 }}}
-(or other version before 7.0.13).  When this happens you need to make sure your xorg-xproto port is up to date.  Use {{{sudo port selfupdate}}} then {{{sudo port upgrade outdated}}} (or at least {{{sudo port upgrade xorg-xproto}}}).
+
+'''Workaround:'''[[BR]]
+
+When this happens you need to make sure your xorg-xproto port is up to date.  Use {{{sudo port selfupdate}}} then {{{sudo port upgrade outdated}}} (or at least {{{sudo port upgrade xorg-xproto}}}).

-------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 .
