> On Sep 9, 2016, at 1:56 PM, Ken Cunningham <[email protected]> > wrote: > > I might dig into the build script and see what's going on in there, but > before I do that is there a way to monkey with the $PATH for the build only, > and then set it back to the user's $PATH when we're done? > > That's cheating, I know.. but I could put ${prefix}/bin/python2.7 at the head > of the $PATH temporarily...
PATH cannot contain filenames, only directory names. I'm reluctant to tell you how to monkey with PATH or what you would add. It'd be better to figure out what the build system is doing. You should also file a ticket against hatari. vq _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
