On Jun 11, 2009, at 06:54, Thomas De Contes wrote:
Le 11 juin 09 à 06:51, Ryan Schmidt a écrit :
Well, a user who types "sudo port selfupdate" causes MacPorts to
build itself from source...
yes but in a "closed" environement (for example i suppose that PATH
is replaced by binpath), like for ports
True. MacPorts clears the environment, and then sets only specific
environment variables, such as PATH=binpath.
is there a simple way to use the system's default PATH, just for
the time to build MacPorts ?
Just do it! Run
export PATH="/bin:/sbin:/usr/bin:/usr/sbin"
before you run the configure, make and make install commands.
That's what I do. Then close the Terminal window to get your
previous PATH back.
ok :-)
i don't like very much to have fixed things (for example binpath
uses a x11prefix path which can vary (i think)),
x11prefix was /usr/X11R6 in Tiger and earlier and /usr/X11 in Leopard
and later. But x11prefix has been removed entirely from MacPorts
trunk and will not exist anymore in MacPorts 1.8.0 and later. Any
required parts of X11 are now installed using MacPorts just like any
other port.
but if you do that, it must be right :-)
Well, it works for me. :)
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
