strange response to selfupdate after installing 1.5
Hi, Just installed version 1.5 of macports (over top of an existing, older version) on an Intel mac and the selfupdate I tried failed with the following output: no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach- o, but wrong architecture while executing "load /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib" ("package ifneeded" script) invoked from within "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "mportinit" line 365) invoked from within "mportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach- o, but wrong architecture I get this same response for any port command, even port all by itself. Sorry if this is old news but I cannot seem to find an email archive to search or an decent FAQ on the Wiki. Any pointers to these resources would also be much appreciated. Cheers, Rob
On Aug 13, 2007, at 18:20, Rob MacLeod wrote:
Just installed version 1.5 of macports (over top of an existing, older version) on an Intel mac and the selfupdate I tried failed with the following output:
no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture while executing "load /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib" ("package ifneeded" script) invoked from within "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "mportinit" line 365) invoked from within "mportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture
I get this same response for any port command, even port all by itself.
Sorry if this is old news but I cannot seem to find an email archive to search or an decent FAQ on the Wiki. Any pointers to these resources would also be much appreciated.
It sounds like part of your MacPorts installation is of the wrong architecture. Have you recently migrated from a PowerPC Mac to an Intel one, and used Migration Assistant to copy data from your old machine, including /opt/local? If so, that's a likely reason for this problem, and I recommend you move /opt/local aside and reinstall MacPorts from scratch and then reinstall all your ports so that they build for Intel.
Thanks Ryan, On Aug 13, 2007, at 7:13 PM, Ryan Schmidt wrote:
On Aug 13, 2007, at 18:20, Rob MacLeod wrote:
Just installed version 1.5 of macports (over top of an existing, older version) on an Intel mac and the selfupdate I tried failed with the following output:
no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture while executing "load /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib" ("package ifneeded" script) invoked from within "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "mportinit" line 365) invoked from within "mportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture
I get this same response for any port command, even port all by itself.
Sorry if this is old news but I cannot seem to find an email archive to search or an decent FAQ on the Wiki. Any pointers to these resources would also be much appreciated.
It sounds like part of your MacPorts installation is of the wrong architecture. Have you recently migrated from a PowerPC Mac to an Intel one, and used Migration Assistant to copy data from your old machine, including /opt/local? If so, that's a likely reason for this problem, and I recommend you move /opt/local aside and reinstall MacPorts from scratch and then reinstall all your ports so that they build for Intel.
Actually, I migrated from another Intel Mac, where I have no such problems running port commands. I have never used Macports on a PPC computer actually--I was a fink user then and migrated to Macports with my first Intel Mac. I have not updated to 1.5 on the "good" machine though, and will see if it is that installation that breaks things. Cheers Rob
participants (2)
-
Rob MacLeod
-
Ryan Schmidt