Changes between Initial Version and Version 1 of Ticket #43809
- Timestamp:
- May 24, 2014, 3:37:08 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #43809 – Description
initial v1 1 {{{2 1 Today I've been trying to run 'port selfupgrade' on my PowerBook G4. It has Mac OS 10.5.8, and XCode version 3.1.4 3 2 4 3 After the command failed on several attempts, I reran with -v to get some information; at the outset, I see: 5 4 5 {{{ 6 6 MacPorts base version 2.2.1 installed, 7 7 MacPorts base version 2.3.0 downloaded. 8 }}} 8 9 9 10 All appears to proceed ok until: 10 11 12 {{{ 11 13 ===> staging to destroot in vendor/tcllib-1.15 12 14 /usr/bin/tclsh8.6-64 `echo ./installer.tcl` \ … … 21 23 Exit code: 2 22 24 Error: Error installing new MacPorts base: command execution failed 25 }}} 23 26 24 27 The invocation of /usr/bin/tclsh8.6-64 seems incorrect; the 'file' command says: 25 28 29 {{{ 26 30 /usr/bin/tclsh8.6-64: Mach-O universal binary with 2 architectures: [ppc64: Mach-O ppc64 executable] [x86_64: Mach-O 64-bit x86_64 executable] 31 }}} 27 32 28 33 On my PowerBook G4, clearly neither of those architectures is going to be any help. … … 30 35 Looks like a better choice would be: 31 36 37 {{{ 32 38 /usr/bin/tclsh8.6: Mach-O universal binary with 2 architectures: [ppc: Mach-O ppc executable] [i386: Mach-O i386 executable] 39 }}} 33 40 34 41 I'll continue to pursue this myself, in an effort to understand why the 64-bit tclsh8.6 is being selected on what's clearly a 32-bit host; but I'm sure someone familiar with MacPorts internals could get there much more quickly. I can provide more info if needed. 35 }}}