On Mon, Mar 25, 2013 at 3:33 AM, Scott Clausen <[email protected]> wrote:
> Hello, > > After a recent update of Macports I now have the following constantly > running in Mountain Lion terminal: > > # MacPorts Installer addition on 2009-11-22_at_17:22:04: adding an > appropriate PATH variable for use with MacPorts. > export > PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin > # Finished adapting your PATH environment variable for use with MacPorts. > # export PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin > # export PATH=usr/local/bin:/usr/local/sbin:/usr/local/mysql/ > ~ > # Setting PATH for MacPython 2.6 > # The orginal version is saved in .bash_profile.pysave > > PATH=/Library/Frameworks/Python.framework/Versions/2.6/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin > export PATH > This sounds like you had something interesting in your .profile and the macports installer didn't understand it. (Specifically, a loop cat-ing a here document comes to mind, but there are other possibilities.) If you're okay with pastebinning your .porfile (or .bash_profile if that's what you have) somewhere then someone can look it over and see what went wrong. -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
