I "run" macports as a regular user... but when I want to run the port command I first "su" to an admin account and then run the port commands with sudo. As far as I know macports requires full privileges to work properly. Likely you could get something working fully as non-admin by installing from source and changing some options, but the installer assumes you want to put it in /opt/local etc.
Scott On Wed, Nov 17, 2010 at 5:30 PM, Potato Soup <[email protected]> wrote: > Ok, I removed it, and then logged into OSX with an admin account and > reinstalled and then did selfupdate. Everything worked fine. So what's the > deal, how do I set it to work from a non Admin account? I never work in an > Admin account for fear of security issues. > ________________________________ > From: Lenore Horner <[email protected]> > To: Potato Soup <[email protected]> > Cc: [email protected] > Sent: Wed, November 17, 2010 8:06:10 PM > Subject: Re: Broken install on new SnowLeopard machine with > MacPorts-1.9.2-10.6-SnowLeopard.dmg > > > On Nov 17, 2010, at 7:55 PM, Potato Soup wrote: > > Hi I just installed the latest SnowLeopard Mac Ports > (MacPorts-1.9.2-10.6-SnowLeopard.dmg) from the website, on my brand new 27" > iMac with SnowLeopard and latest xcode, and when running port, it fails > with: > dlopen(/opt/local/share/macports/Tcl/macports1.0/MacPorts.dylib, 10): no > suitable image found. Did find: > /opt/local/share/macports/Tcl/macports1.0/MacPorts.dylib: no matching > architecture in universal wrapper > while executing > "load /opt/local/share/macports/Tcl/macports1.0/MacPorts.dylib" > ("package ifneeded macports 1.0" script) > invoked from within > "package require macports" > (file "/opt/local/bin/port" line 39) > > I searched and all I could find was examples of people having this issue > when upgrading from older OSX versions, not a brand new SLeopard. I am > stumped and I now have a broken install. Any help would be greatly > appreciated. > > Did you bring anything over from a previous Mac? If you did this in any > automatic way, you probably brought over your old /opt/local built for the > wrong OS. If not, I'm stumped but I'm sure someone else will know. > > > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
