= Recurrent Problems on Leopard =

== environment variables become blank between configure and build phases ==
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.

This problem can be worked around by cleaning the work area of the affected port (`sudo port clean --work foo`) and then running the `port install` (or `port upgrade`) command again.

Here is [http://lists.macosforge.org/pipermail/macports-users/2008-April/009991.html an analysis of the problem] by Bryan Blackburn.

This should be fixed on trunk (r36719, r36722, r39016, r39017) but the fix isn't part of MacPorts 1.6.0. It will be in the next version of MacPorts.

(I have a similar problem doing sudo port install seamonkey on 10.5.4 on an
iBook(ppc).  So I edited the above mentioned files as indicated and did
cd  /opt/local/var/macports/sources/rsync.macports.org/release/base
sudo ./configure
sudo make all
sudo make install
and it didn't help.. 

to wit:
--->  Building seamonkey with target all
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_seamonkey/work/mozilla" && make all " returned error 2
Command output: o host_include. -c  -DINCLUDEDIR=\"/usr/include\" -DOBJSUFFIX=\".\"   -I/include/mkdepend -I/include  -I/sdk/include  /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_seamonkey/work/mozilla/config/mkdepend/include.c
make[3]: o: Command not found
make[3]: [host_include.] Error 127 (ignored)
.... etc ending in..
make[2]: *** [export] Error 127
make[1]: *** [export] Error 2
make: *** [all] Error 2

Error: Status 1 encountered during processing.


I notice that there is a [3] after the make,  at the time of the first error, so
it seems to be an environment variable setting problem of some kind)

== `ld: cycle in dylib re-exports with /usr/X11/lib/libGL.dylib` ==
This is the result of a misfeature in Leopard's linker. See Apple's Technical Q&A on the subject [http://developer.apple.com/qa/qa2007/qa1567.html here]. It can generally be fixed by adding the following to the portfile inside a `platform darwin 9` block:
{{{
configure.ldflags-append 	-dylib_file \
			/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:\
			/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
}}}

== macfuse fails to build ==
There is an issue with building macfuse on 10.5, documented in ticket #15889.  If it fails to build for you with the error message
{{{
undefined local variable or method `trans' for <UNDEFINED> ... </>:REXML::Document
}}}
then you've run into #15889.  A possible workaround has been listed in the ticket.