Changes between Version 34 and Version 35 of ProblemHotlist


Ignore:
Timestamp:
Aug 10, 2008, 11:46:56 PM (16 years ago)
Author:
raimue (Rainer Müller)
Comment:

Move the more common problems to the top

Legend:

Unmodified
Added
Removed
Modified

  • ProblemHotlist

    v34 v35  
    33(Note, if you're using Mac OS X 10.5.x, be sure also to check the LeopardProblems page)
    44
    5 == 1. Fetch failures ==
     5== .profile not set up ==
     6
     7After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It will be fixed in the next release of MacPorts.
     8
     9To work around the problem, download the `postflight` script and run it manually, like this:
     10
     11{{{
     12curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight
     13}}}
     14
     15This will set up your `.profile` for you. After the `.profile` is set up, the script will attempt to run `sudo port selfupdate` but will fail. This is normal in this case. Please ignore the permission errors the `rsync` process will print. When the script finishes, you should run `sudo port selfupdate` manually.
     16
     17To get the terminal to notice the new `.profile`, close your terminal window and open a new one.
     18
     19Instead of downloading and running the `postflight` script from the repository, you could set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].
     20
     21== man port fails with error message ==
     22If you get following error message, when trying to access the man page for port or installed ports.
     23{{{
     24Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>")
     25No manual entry for port
     26}}}
     27Add the following line to your .profile or .bash_profile.
     28{{{
     29export MANPATH=/opt/local/share/man:${MANPATH}
     30}}}
     31Tracked in ticket #13444.
     32
     33== Fetch failures ==
    634
    735If 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.
    … …  
    2351'''Note:''' Checksum failures after a fetch are typically a separate issue.  See the [wiki:FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit FAQ].
    2452
    25 == 2. A port failed to build, upgrade, or run with a message referring to libintl.3.dylib ==
     53== A port failed to build, upgrade, or run with a message referring to libintl.3.dylib ==
    2654
    2755{{{
    … …  
    73101}}}
    74102
    75 == 3. A port failed to build with a message referring to 1/lib: No such file or directory ==
     103== A port failed to build with a message referring to 1/lib: No such file or directory ==
    76104
    77105{{{
    … …  
    93121port clean --work <port>
    94122}}}
    95 
    96 == 4. .profile not set up ==
    97 
    98 After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It will be fixed in the next release of MacPorts.
    99 
    100 To work around the problem, download the `postflight` script and run it manually, like this:
    101 
    102 {{{
    103 curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight
    104 }}}
    105 
    106 This will set up your `.profile` for you. After the `.profile` is set up, the script will attempt to run `sudo port selfupdate` but will fail. This is normal in this case. Please ignore the permission errors the `rsync` process will print. When the script finishes, you should run `sudo port selfupdate` manually.
    107 
    108 To get the terminal to notice the new `.profile`, close your terminal window and open a new one.
    109 
    110 Instead of downloading and running the `postflight` script from the repository, you could set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].
    111 
    112 == 5. man port fails with error message ==
    113 If you get following error message, when trying to access the man page for port or installed ports.
    114 {{{
    115 Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>")
    116 No manual entry for port
    117 }}}
    118 Add the following line to your .profile or .bash_profile.
    119 {{{
    120 export MANPATH=/opt/local/share/man:${MANPATH}
    121 }}}
    122 Tracked in ticket #13444.