Changes between Version 19 and Version 20 of LeopardProblems


Ignore:
Timestamp:
Dec 14, 2008, 9:44:26 AM (15 years ago)
Author:
tobypeterson
Comment:

simplify, simplify, simplify

Legend:

Unmodified
Added
Removed
Modified

  • LeopardProblems

    v19 v20  
    22
    33== environment variables become blank ==
    4 This manifests as error messages like: `unable to execute -DNDEBUG: No such file or directory`. ($CC is an empty string, so what was meant to be the the first argument to the compiler is now the first thing on the command line, and is treated as a command name by the shell.) Seems to frequently occur when building Python modules; see #13930.
     4This manifests as error messages similar to the following.
     5{{{
     6unable to execute -DNDEBUG: No such file or directory
     7}}}
     8(`$CC` is an empty string, so what was meant to be the the first argument to the compiler is now the first thing on the command line, and is treated as a command name by the shell.)
    59
    6 This problem can be worked around by cleaning the work area of the affected port using
    7 {{{
    8 sudo port clean --work foo
    9 }}}
    10 and then running the `port install` (or `port upgrade`) command again.
    11 
    12 Here is [http://lists.macosforge.org/pipermail/macports-users/2008-April/009991.html an analysis of the problem] by Bryan Blackburn.
    13 
    14 This is fixed in MacPorts 1.7.0 (r36719, r36722, r39016, r39017, r41603, r41639, r41650, r41651).
     10This issue is resolved in [http://www.macports.org/install.php MacPorts 1.7.0].
    1511
    1612== `ld: cycle in dylib re-exports with /usr/X11/lib/libGL.dylib` ==
    17 This is the result of a misfeature in Leopard's linker; see Apple [http://developer.apple.com/qa/qa2007/qa1567.html Technical Q&A QA1567]. Users encountering this issue should upgrade to the latest [http://developer.apple.com/technology/xcode.html Xcode Tools] release.
     13This is the result of a misfeature in Leopard's linker; see Apple [http://developer.apple.com/qa/qa2007/qa1567.html Technical Q&A QA1567]. This can be fixed by upgrading to the latest [http://developer.apple.com/technology/xcode.html Xcode Tools] release.
    1814
    1915== macfuse fails to build ==
    20 There is an issue with building macfuse on versions of Leopard prior to 10.5.5, documented in ticket #15889.  If it fails to build for you with the error message
     16On versions of Leopard prior to 10.5.5, macfuse fails to build with the following error message (#15889).
    2117{{{
    2218undefined local variable or method `trans' for <UNDEFINED> ... </>:REXML::Document
    2319}}}
    24 then you've run into #15889. Upgrading to 10.5.5 or later will fix this, or if you can't upgrade for some reason, a possible workaround is given in the ticket.
     20Updating to 10.5.5 or later using Software Update should resolve this issue.
    2521
    2622== `/usr/X11/lib/libXrandr.2.0.0.dylib: No such file or directory` ==
    27 This is a problem encountered when trying to install gtk2 on some Leopard machines (#14592). The .la files in `/usr/X11/lib` refer to the wrong library.[[BR]]
    28 According to #17008, upgrading X11 using Software Update should fix this.[[BR]]
    29 If not, upgrading to the latest XQuartz (http://xquartz.macosforge.org/) certainly fixes the problem.[[BR]]
    30 Alternate solutions are given in tickets  #14592 and #17008.
     23This is a problem encountered when trying to install gtk2 on some Leopard machines (#14592, #17008). The .la files in `/usr/X11/lib` refer to the wrong library.
    3124
     25Upgrading X11 using Software Update should fix this; if not, install the latest [http://xquartz.macosforge.org/ Xquartz] release.