#13517: gtkglext 1.2 configure: error -- build failure OSX 10.5 -----------------------------------------+---------------------------------- Reporter: michaelt@… | Owner: rowue@… Type: defect | Status: reopened Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Resolution: | Keywords: gtkglext gwyddion mesa Port: gtkglext | -----------------------------------------+---------------------------------- Comment(by jeremyhu@…): Ok, then can you please debug a little more? It is adding X11_DIR=${x11prefix} to the {{{ ---> Building mesa DEBUG: Executing org.macports.build (mesa) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_rowue_macports_dports_x11_mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/usr/X11R6' }}} But the only place it does that is in a check for the existence of libX11.dylib: {{{ ~/src/macports-trunk/dports/x11/mesa $ grep -C2 X11_DIR Portfile # This next hunk supports building -system_x11 mesa on a system that is otherwise +system_x11 if {! [file exists ${prefix}/lib/libX11.dylib]} { build.args-append X11_DIR=${x11prefix} destroot.args-append X11_DIR=${x11prefix} } } }}} So I'm wondering if the build.args are getting set when the mesa Portfile is processed for dependencies libX11 isn't installed, we update build.args libX11 isn't installed, we install libX11 then come back to mesa (this is jumping a few steps through libXext, but you get the idea) we come back to mesa to build it with our libX11 installed, but our build.args is already set assuming there is no libX11 ...? Is that happening? That doesn't seem right to me... -- Ticket URL: <http://trac.macports.org/ticket/13517#comment:42> MacPorts <http://www.macports.org/> Ports system for Mac OS