Changes between Version 44 and Version 45 of ProblemHotlist
- Timestamp:
- Jul 26, 2009, 10:47:29 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProblemHotlist
v44 v45 3 3 (Note, if you're using Mac OS X 10.5.x, be sure also to check the LeopardProblems page) 4 4 5 == man port fails with error message == 6 If you get following error message, when trying to access the man page for port or installed ports. 5 == man port fails with error message == #manpath 6 7 '''Error message:'''[[BR]] 7 8 {{{ 9 $ man port 8 10 Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>") 9 11 No manual entry for port 10 12 }}} 13 14 '''Workaround:'''[[BR]] 15 11 16 Add the following line to your .profile or .bash_profile. 12 17 {{{ 13 18 unset MANPATH 14 19 }}} 15 Tracked in ticket #13444. 20 21 '''Ticket:''' #13444[[BR]] 16 22 17 23 == port fails with: Image error: /opt/local/bin/a2p... == #perl5-image-error 18 The perl ports are currently in flux, and can potentially cause issues resulting in the error message 24 25 '''Error message:'''[[BR]] 19 26 {{{ 20 27 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. 21 28 }}} 29 30 The perl ports recently changed the paths for builtin modules, which can potentially cause issues resulting in this error message. 31 32 '''Workaround:'''[[BR]] 22 33 The current method to get around this issue is to run 23 34 {{{ … … 26 37 then run your initial install command. 27 38 28 == Fetch failures == 39 == Fetch failures == #fetch-failures 29 40 30 41 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. … … 73 84 '''Ticket:''' #18583[[BR]] 74 85 75 == A port failed to build, upgrade, or run with a message referring to libintl.3.dylib == 86 == A port failed to build, upgrade, or run with a message referring to libintl.3.dylib == #libintl 76 87 88 '''Error message:'''[[BR]] 77 89 {{{ 78 90 dyld: Library not loaded: /opt/local/lib/libintl.3.dylib 79 91 }}} 80 92 93 '''Explanation:'''[[BR]] 81 94 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. 82 95 96 '''Workaround:'''[[BR]] 83 97 Here is a script that can tell you what ports you have installed that depend on gettext. 84 98 … … 123 137 }}} 124 138 125 == A port failed to build with a message referring to 1/lib: No such file or directory == 139 == A port failed to build with a message referring to 1/lib: No such file or directory == #lib-spaces 126 140 141 '''Error message:'''[[BR]] 127 142 {{{ 128 143 apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory … … 130 145 }}} 131 146 147 '''Explanation:'''[[BR]] 132 148 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. 133 149 … … 138 154 /usr/lib/ruby 1/ 139 155 }}} 156 157 '''Workaround:'''[[BR]] 140 158 141 159 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: … … 155 173 156 174 == Can't install python modules because of unrecognized --no-user-cfg == #no-user-cfg 157 While trying to install python modules, if it fails with the message 175 176 '''Error message:'''[[BR]] 158 177 {{{ 159 178 error: option --no-user-cfg not recognized 160 179 }}} 161 your python port is outdated. For py25-* modules, you need to upgrade python25, for py26-*, python26, and for py30-*, python30. 180 181 '''Workaround:'''[[BR]] 182 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. 162 183 163 184 == A port fails to build due to XPROTO == #xproto 185 186 '''Error message:'''[[BR]] 164 187 When building a port which depends on some X11-based ports, it fails with 165 188 {{{ 166 Requested 'xproto >= 7.0. 13' but version of Xproto is 7.0.11189 Requested 'xproto >= 7.0.XY' but version of Xproto is 7.0.11 167 190 }}} 168 (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}}}). 191 192 '''Workaround:'''[[BR]] 193 194 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}}}).