wiki:LeopardProblems

Version 23 (modified by jmroot (Joshua Root), 16 years ago) (diff)

libXdamage is affected by the bad .la files too

Recurrent Problems on Leopard

environment variables become blank

This manifests as error messages similar to the following.

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

This issue is resolved in MacPorts 1.7.0.

ld: cycle in dylib re-exports with /usr/X11/lib/libGL.dylib

This is the result of a misfeature in XCode 3.0.0's linker; see Apple Technical Q&A QA1567. This can be fixed by upgrading to the latest Xcode Tools release.

macfuse fails to build

On versions of Leopard prior to 10.5.5, macfuse fails to build with the following error message (#15889).

undefined local variable or method `trans' for <UNDEFINED> ... </>:REXML::Document

Updating to 10.5.5 or later using Software Update should resolve this issue.

/usr/X11/lib/libXrandr.2.0.0.dylib: No such file or directory

This is a problem encountered when trying to install gtk2 on some Leopard machines (#14592, #17008, #17356). The .la files in /usr/X11/lib refer to the wrong library. You may also see this problem with other X libraries such as libXdamage.

Upgrading to the latest Xquartz release should fix this problem.