On 11/25/07, Ryan Schmidt <[EMAIL PROTECTED]> wrote:
>
>
> On Nov 25, 2007, at 13:29, paul beard wrote:
>
> > On 11/25/07, Ryan Schmidt wrote:
> >
> >> What Mac do you have? Did you previously have a different Mac, back
> >> when you originally installed MacPorts? Maybe you used Migration
> >> Assistant to transfer everything (including MacPorts) from the old
> >> Mac to the new Mac? IF the old Mac was PowerPC-based and the new one
> >> is Intel-based, that could explain the error you're seeing, and you
> >> should really uninstall everything and start over. You can use "port
> >> installed" to see what ports are installed.
> >
> > How will that work if the port command doesn't run?
>
> Good question. It might not work then. We might have to dig deeper to
> see what's installed. Like this:
>
> cd /opt/local/var/macports/receipts/
> find . -name receipt.bz2 | sed -E 's%^\./(.*)/(.*)/receipt\.bz2$%\1 @
> \2%'


Watch the line-wrap: that \2% should stay on the same line. Same below . . .
.

Or, for the user's version of DarwinPorts before the new layout, I
> hope this is it:
>
> cd /opt/local/var/db/dports/receipts/
> find . -name receipt.bz2 | sed -E 's%^\./(.*)/(.*)/receipt\.bz2$%\1 @
> \2%'
>
>
> >> It also sounds like your PATH is not correct since it can't find the
> >> port command.
> >
> > Actually, it does seem to find it OK: if the user types 'port
> > <something>' and the result is
> >
> > Error: /opt/local/bin/port: Failed to initialize ports system, no
> > suitable image found.  Did find:
> >        /opt/local/share/darwinports/Tcl/pextlib1.0/Pextlib.dylib:
> > mach-o, but wrong architecture
> >
> > it sounds like the command is there but if the error message is
> > right, that the architecture is wrong.
>
> It sounds to me like the user is having to run "/opt/local/bin/port"
> because when just "port" is run this error was shown:
>
> On Nov 25, 2007, at 11:14, tania habib wrote:
>
> > On Nov 25, 2007 2:11 PM, William Davis wrote:
> >>
> >
> >> Did you try :
> >> sudo port -d selfupdate
> >> ?
> >
> > Yes I did, but it comes with the error that "port:command not found".
> > I feel there is some path problem. Can please guide me through the
> > procedure of setting the path variable in X11!
>
>
>


-- 
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to