The qt3-mac used to work with this: configure.env QMAKESPEC='' QTDIR='' DYLD_LIBRARY_PATH='' build.env QMAKESPEC='' QTDIR='' DYLD_LIBRARY_PATH="${worksrcpath}/lib" but now using port -d -v install qt3-mac, you can see that the environments are not passed to the configure and build steps. Can somebody who knows this part of the code take a look? Also, having a standard set up Portfile's that ensure that things work correctly would be a good thing. We seem to break things and only later find out that something has changed. In this case, the Portfile could set the env and the Makefile could ensure that the environment is indeed set. Another thing is to have a beefy build box that builds a large number of Portfile's before a new release and looks for any regressions in ports that used to build. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <blair@orcaware.com> Subversion training, consulting and support http://www.orcaware.com/svn/