On Apr 23, 2013, at 16:43, René J.V. Bertin wrote:

> You don't have anything in your path or otherwise accessible to the build 
> procedure that could cause interference (say in /usr/local)?

MacPorts ignores your PATH; instead, it uses the value of binpath in 
macports.conf, specifically so that other software you might have installed 
won't affect MacPorts.

_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to